Linux Kernel up to 4.19 phy-ocelot-serdes.c out-of-bounds

Summaryinfo

A vulnerability classified as critical has been found in Linux Kernel up to 4.19. The affected element is an unknown function of the file drivers/phy/mscc/phy-ocelot-serdes.c. Performing a manipulation results in out-of-bounds. This vulnerability is reported as CVE-2018-20854. The attack requires a local approach. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 4.19 (Operating System). This affects some unknown processing of the file drivers/phy/mscc/phy-ocelot-serdes.c. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in the Linux kernel before 4.20. drivers/phy/mscc/phy-ocelot-serdes.c has an off-by-one error with a resultant ctrl->phys out-of-bounds read.

The weakness was disclosed 07/26/2019 as confirmed git commit (GIT Repository). The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2018-20854 since 07/26/2019. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The reason for this vulnerability is this part of code:

for (i = 0; i <= SERDES_MAX; i++) {

Upgrading to version 4.20 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. The vulnerability will be addressed with the following lines of code:

for (i = 0; i < SERDES_MAX; i++) {

The entries VDB-138838, VDB-138839, VDB-138853 and VDB-138854 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 4.0
• 4.1
• 4.2
• 4.3
• 4.4
• 4.5
• 4.6
• 4.7
• 4.8
• 4.9
• 4.10
• 4.11
• 4.12
• 4.13
• 4.14
• 4.15
• 4.16
• 4.17
• 4.18
• 4.19

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion