net: phy: dp83869: fix memory corruption when enabling fiber
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.227, 5.15.168, 6.1.113, 6.6.57, 6.11.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: net: phy: dp83869: fix memory corruption when enabling fiber When configuring the fiber port, the DP83869 PHY driver incorrectly calls linkmode_set_bit() with a bit mask (1 << 10) rather than a bit number (10). This corrupts some other memory location -- in case of arm64 the priv pointer in the same structure. Since the advertising flags are updated from supported at the end of the function the incorrect line isn't needed at all and can be removed.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From a29de52ba2a156873505d8b8cef44e69925b8114 · fixed in 21b5af7f0c99b3bf1fd02016e6708b613acbcaf4; From a29de52ba2a156873505d8b8cef44e69925b8114 · fixed in ad0d76b8ee5db063791cc2e7a30ffc9852ac37c4; From a29de52ba2a156873505d8b8cef44e69925b8114 · fixed in c1944b4253649fc6f2fb53e7d6302eb414d2182c; From a29de52ba2a156873505d8b8cef44e69925b8114 · fixed in 9ca634676ff66e1d616259e136f96f96b2a1759a; From a29de52ba2a156873505d8b8cef44e69925b8114 · fixed in e3f2de32dae35bc7d173377dc97b5bc9fcd9fc84; From a29de52ba2a156873505d8b8cef44e69925b8114 · fixed in a842e443ca8184f2dc82ab307b43a8b38defd6a5
- Linux Linux
5.10
- KernelLinux
From 5.10.0 · fixed in 5.10.227; From 5.11.0 · fixed in 5.15.168; From 5.16.0 · fixed in 6.1.113; From 6.2.0 · fixed in 6.6.57; From 6.7.0 · fixed in 6.11.4