CVE-2026-80731 — net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header
In the Linux kernel, the following vulnerability has been resolved: net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header dev_validate_header() reads dev->hard_header_len directly when zero-padding short link layer headers for CAP_SYS_RAWIO holders: if (capable(CAP_SYS_RAWIO)) { memset(ll_header + len, 0, dev->hard_header_len - len); return true; } Packet send paths call dev_validate_header() on skbs whose headroom was allocated from an earlier hard_header_len read. If the device is reconfigured so that dev->hard_header_len increases before validation, the memset writes past the reserved buffer, an out-of-bounds write. This out-of-bounds write is masked in some SOCK_RAW paths today because the same concurrent increase can first make skb_push() exceed the reserved headroom and trigger skb_under_panic(). Remove the zero-padding branch before making those hard_header_len reads consistent, so the snapshot fixes do not turn a loud panic into a silent overwrite. This path is only reached for variable length L2 protocols, where len < hard_header_len but len >= min_header_len. No remaining in-tree variable length L2 protocol implements header_ops->validate, and the CAP_SYS_RAWIO bypass that zero-pads and accepts short headers has no real value beyond allowing testing of intentionally malformed input. Drop the CAP_SYS_RAWIO branch. The remaining reads of dev->hard_header_len in dev_validate_header() are comparisons only and have no memory safety impact.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version f58a6c08ebdfa978178bbca78c2ba744a2665912version 4.6≥ 4.5.2 and < 4.6≥ 4.4.8 and < 4.5≥ 4.1.28 and < 4.2≥ 3.16.36 and < 3.17≥ 3.2.80 and < 3.2.81version 6804052fa9d86e9a512c88b24a5debbfc1a490fc and 11 moreversion 8b8d278aa4de9335682bbd4a3bb619af015c859eversion 1df16498dfd0d5a129bdf2982d9a08df73e8923d≥ b5518429e70cd783b8ca52335456172c1a0589f6 and < 53fd7f912c0877647d6a1e1877f5ea8535ee0b4a≥ 2793a23aacbd754dbbb5cb75093deb7e4103bace and < 3b9a324e646d3657a8d9806dfbfe4f3e4066e882≥ 2793a23aacbd754dbbb5cb75093deb7e4103bace and < fc902f52a02298c7432b2334c0c82a2885a1a8b6≥ 2793a23aacbd754dbbb5cb75093deb7e4103bace and < dbb30dc943a93e083f1e531bfdc6779e57de40d0≥ 2793a23aacbd754dbbb5cb75093deb7e4103bace and < 74e035f07f53feca09e2352e77fccb09cad5e208≥ 2793a23aacbd754dbbb5cb75093deb7e4103bace and < 99df6b7a713f96eda206680d100b76e15f9d9b69≥ 2793a23aacbd754dbbb5cb75093deb7e4103bace and < b0f92a5731dc82556a9ae005cc35f71ab136307b≥ 2793a23aacbd754dbbb5cb75093deb7e4103bace and < 8fc9816404166a90ed8d544dc52482fafffb6d9f≥ 2793a23aacbd754dbbb5cb75093deb7e4103bace and < fa6d98dd925e72fc028b26a0cbbff9d2f0601ff6 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.8
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
9 on the record
- git.kernel.org/stable/c/fc902f52a02298c7432b2334c0c82a2885a1a8b6
- git.kernel.org/stable/c/fa6d98dd925e72fc028b26a0cbbff9d2f0601ff6
- git.kernel.org/stable/c/dbb30dc943a93e083f1e531bfdc6779e57de40d0
- git.kernel.org/stable/c/8fc9816404166a90ed8d544dc52482fafffb6d9f
- git.kernel.org/stable/c/99df6b7a713f96eda206680d100b76e15f9d9b69
- git.kernel.org/stable/c/b0f92a5731dc82556a9ae005cc35f71ab136307b
- git.kernel.org/stable/c/53fd7f912c0877647d6a1e1877f5ea8535ee0b4a
- git.kernel.org/stable/c/74e035f07f53feca09e2352e77fccb09cad5e208
- git.kernel.org/stable/c/3b9a324e646d3657a8d9806dfbfe4f3e4066e882
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 13h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 13h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80731 is "net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.