ipmi: ipmb: validate write message length
In the Linux kernel, the following vulnerability has been resolved: ipmi: ipmb: validate write message length ipmb_write() read message fields before validating the length byte. A zero or short write can read uninitialized stack bytes. A length smaller than the SMBus header underflows the block write length. Require a non-empty buffer and the minimum IPMB request length. Also require the length byte plus payload before parsing the message.
- Published
- Sep 11, 2026
- Updated
- Sep 14, 2026
- EPSS
- 0.2% · 5th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.3affected
- 51bd6f291583684f495ea498984dfc22049d7fd2 and later · before 8990c7f6bfc1e7689b7012a7d4d0efb9f07a9c89affected · git
- 51bd6f291583684f495ea498984dfc22049d7fd2 and later · before 94f8d20153e348c79bc14dc25f873470518892daaffected · git
- 51bd6f291583684f495ea498984dfc22049d7fd2 and later · before e527cd4e80066e1ed070fdc7c705bde340cdcc62affected · git
- 51bd6f291583684f495ea498984dfc22049d7fd2 and later · before 7d66d54b974cff0a959e188af844d2d110422767affected · git
- 51bd6f291583684f495ea498984dfc22049d7fd2 and later · before 60939bcda6f3f104ef456fdbf3cc5733c0720fb1affected · git
- 51bd6f291583684f495ea498984dfc22049d7fd2 and later · before 5719431ca2b5fa26560bb38f6202f8b97fa3bbb0affected · git
- 51bd6f291583684f495ea498984dfc22049d7fd2 and later · before a84c6e3d188f2c6e674910929eb790634299d6d5affected · git
- 51bd6f291583684f495ea498984dfc22049d7fd2 and later · before 53637506884dbd5c91a89b1a3547d99d80f8ed2caffected · git
- before 5.3not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | all versions | — |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 53637506884dbd5c91a89b1a3547d99d80f8ed2c | Vendor (CNA) |
| Linux Linux | 5719431ca2b5fa26560bb38f6202f8b97fa3bbb0 | Vendor (CNA) |
| Linux Linux | 60939bcda6f3f104ef456fdbf3cc5733c0720fb1 | Vendor (CNA) |
| Linux Linux | 7d66d54b974cff0a959e188af844d2d110422767 | Vendor (CNA) |
| Linux Linux | 8990c7f6bfc1e7689b7012a7d4d0efb9f07a9c89 | Vendor (CNA) |
| Linux Linux | 94f8d20153e348c79bc14dc25f873470518892da | Vendor (CNA) |
| Linux Linux | a84c6e3d188f2c6e674910929eb790634299d6d5 | Vendor (CNA) |
| Linux Linux | e527cd4e80066e1ed070fdc7c705bde340cdcc62 | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/53637506884dbd5c91a89b1a3547d99d80f8ed2c
- git.kernel.org/stable/c/5719431ca2b5fa26560bb38f6202f8b97fa3bbb0
- git.kernel.org/stable/c/60939bcda6f3f104ef456fdbf3cc5733c0720fb1
- git.kernel.org/stable/c/7d66d54b974cff0a959e188af844d2d110422767
- git.kernel.org/stable/c/8990c7f6bfc1e7689b7012a7d4d0efb9f07a9c89
- git.kernel.org/stable/c/94f8d20153e348c79bc14dc25f873470518892da
- git.kernel.org/stable/c/a84c6e3d188f2c6e674910929eb790634299d6d5
- git.kernel.org/stable/c/e527cd4e80066e1ed070fdc7c705bde340cdcc62
Vendor advisories and official records. Exploit/PoC links are deliberately left out.