Security readout for executives and security teams
Plain-English summary
A Linux RTL9300 I2C driver flaw can turn an unsupported zero-length request into a 16-byte write. On devices such as SFP modules with writable EEPROM, this may overwrite configuration data and make the module unusable. Exploitation requires local, low-privileged access; no confidentiality impact is identified.
Executive priority
Prioritize affected network or embedded systems controlling valuable or difficult-to-replace modules. The flaw is not remotely exploitable according to the supplied CVSS data, but successful triggering can corrupt hardware configuration and cause operational outages. Patch during the next urgent maintenance window; accelerate where writable SFP EEPROM and accessible local interfaces coexist.
Technical view
The RTL9300 transfer configuration accepted a zero length although hardware supports only 1–16 bytes. The calculation `(len - 1) & 0xf` underflows for zero and programs a 16-byte transfer. An SMBus Quick Write can therefore become an unintended 16-byte write. The kernel fix adds explicit length validation and a zero-length quirk.
Likely exposure
Exposure is limited to Linux systems using the RTL9300 I2C controller driver where local users or software can initiate affected SMBus operations. Risk is greatest when attached components, including SFP modules, contain EEPROM that is not write-protected. The supplied version data identifies Linux 6.13 through affected 6.16.8/6.17 boundaries, but its exact range representation is ambiguous.
Exploitation context
The CVSS vector describes local access, low complexity, low privileges, and no user interaction, with high integrity and availability impact. The supplied record is not in KEV and provides no evidence of active exploitation. The documented destructive behavior is technically concrete, but real-world reach depends on driver use, hardware, permissions, and EEPROM protection.
Researcher notes
The central defect is integer underflow mapped through a four-bit hardware length field. Zero becomes the encoded maximum of 16 bytes rather than being rejected. Researchers should verify downstream backports and the exact affected-version boundaries because the supplied structured version list is unclear. No exploit code, public weaponization, or active campaign evidence is provided.
Mitigation direction
- Update to a vendor-supported kernel containing the referenced RTL9300 I2C fix.
- Check Linux distribution advisories for precise fixed versions and backport status.
- Prevent zero-length SMBus Quick operations on affected systems until patched.
- Enable EEPROM write protection where supported and operationally appropriate.
- Restrict untrusted local access to interfaces capable of initiating I2C or SMBus transfers.
Validation and detection
- Confirm whether the RTL9300 I2C controller driver is present and active.
- Inventory kernel versions and compare vendor backports with both referenced stable commits.
- Identify attached SFP modules or other components with writable, unprotected EEPROM.
- Review whether local low-privileged processes can initiate SMBus Quick operations.
- Validate fixes only with non-destructive tests in isolated hardware or vendor-approved procedures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-191: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-39928 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H1.85.2LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/c91382328fc89f73144d5582f2d8f1dd3e41c8f7CVE reference, Linux
- https://git.kernel.org/stable/c/06418cb5a1a542a003fdb4ad8e76ea542d57cfbaCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Integer Underflow (Wrap or Wraparound)
Integer Underflow (Wrap or Wraparound) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.