Security readout for executives and security teams
Plain-English summary
CVE-2025-22104 is a Linux kernel ibmvnic driver bug. When the driver prints hex dumps, it could read past the end of a buffer. Public sources show a kernel fix and KASAN detection, but no CVSS score or known exploitation.
Executive priority
Treat as a focused kernel maintenance issue, not an emergency based on current evidence. Prioritize IBM virtual NIC-dependent Linux systems and incorporate fixes into normal patch cycles unless vendor guidance raises severity.
Technical view
The ibmvnic driver previously cast buffers to 8-byte values for hex dump logging. If the buffer length was not divisible by eight, an out-of-bounds read could occur. The fix replaces that behavior with a helper-based loop using hex_dump_to_buffer.
Likely exposure
Exposure is likely limited to Linux systems using the ibmvnic driver. Organizations without that driver loaded or without affected kernel builds are unlikely to be exposed. Version impact should be confirmed through distribution kernel advisories.
Exploitation context
The sources describe a read buffer overflow found by KASAN during ibmvnic_login. There is no KEV listing and no cited evidence of active exploitation. The practical impact is not fully characterized in the provided sources.
Researcher notes
Evidence is limited to the CVE record and Linux stable commits. No CVSS, CWE, exploitability assessment, or active exploitation evidence is provided. Validate exact affected ranges through downstream distribution advisories because kernel fixes are often backported.
Mitigation direction
- Apply Linux kernel or distribution updates containing the referenced ibmvnic fix.
- Check vendor guidance for affected kernel versions and backported fixes.
- Prioritize systems that load or depend on the ibmvnic driver.
Validation and detection
- Inventory Linux hosts for kernels using the ibmvnic driver.
- Confirm installed kernels include the referenced stable commits or vendor backports.
- Review kernel logs for KASAN slab-out-of-bounds reports in ibmvnic_login.
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.
CVE-2025-22104 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
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.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/ae6b1d6c1acee3a2000394d83ec9f1028321e207CVE reference, Linux
- https://git.kernel.org/stable/c/d93a6caab5d7d9b5ce034d75b1e1e993338e3852CVE 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.