CVE-2026-74582 — packet: use consistent hard_header_len in non-ring send paths
In the Linux kernel, the following vulnerability has been resolved: packet: use consistent hard_header_len in non-ring send paths packet_snd() reads dev->hard_header_len multiple times while allocating and constructing an skb. Device reconfiguration can change this value concurrently, for example through bonding device type changes. For SOCK_RAW, packet_snd() can save a larger value in reserve and later allocate headroom using a smaller value. Moving skb->data back by reserve then places it before skb->head, and the following copy from userspace can attempt an out-of-bounds write. packet_sendmsg_spkt() has the same issue because it calculates its reservation and header offset from separate reads before dropping the RCU read lock to allocate the skb. Add LL_RESERVED_SPACE_EX() for callers that already saved a header length. Read hard_header_len once in packet_snd() and use it for allocation and construction. In packet_sendmsg_spkt(), preserve the allocation-time value through the device lookup retry. The separate SOCK_DGRAM consistency problem between hard_header_len and header_ops->create is not addressed here.
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
- EPSS 0.1% (30-day exploitation probability)+0
- 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 d9fb8cc230b2a4757e9fe4f81468f81212d4deaaversion 4.17≥ 4.16.12 and < 4.17≥ 4.14.44 and < 4.15≥ 4.9.103 and < 4.10≥ 4.4.133 and < 4.5version 8809ae6747e760e6f1d2453ceb08c9bcc4939766version 01a658c1b9d4b5393c38d5a92d9112ab1425382a and 9 moreversion 6190cce26e40bf71c4d375b21eea74bb07b6a0f3≥ b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba and < bcd4df60ac9481b1ceffdfe5ec38fe51dcaae812≥ b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba and < 03390aa32e669cc4ecd7d34108e2e1afc13d689d≥ b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba and < b06b6fce6d7deaf7238e09b48ce3b1125ff41acd≥ b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba and < 5bb10753d428aadfc356a2bfe9acea09c82a62ec≥ b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba and < 9052756290962ffb9a661bcf319e92dedaaedfed≥ b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba and < 91f041451f967cd87ed722a8f43c0b767a64f1a0≥ b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba and < 142e287b3a25cfe909215177c23243e7fc5ae2b1≥ b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba and < 78a47127e33c340bc6d38dcc4552a094b4f5cc77 |
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 | — | — | GitHub, Inc. via GitHub Security Advisories |
| 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.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
10 on the record
- git.kernel.org/stable/c/78a47127e33c340bc6d38dcc4552a094b4f5cc77
- git.kernel.org/stable/c/bcd4df60ac9481b1ceffdfe5ec38fe51dcaae812
- git.kernel.org/stable/c/03390aa32e669cc4ecd7d34108e2e1afc13d689d
- git.kernel.org/stable/c/9052756290962ffb9a661bcf319e92dedaaedfed
- git.kernel.org/stable/c/91f041451f967cd87ed722a8f43c0b767a64f1a0
- git.kernel.org/stable/c/b06b6fce6d7deaf7238e09b48ce3b1125ff41acd
- git.kernel.org/stable/c/5bb10753d428aadfc356a2bfe9acea09c82a62ec
- nvd.nist.gov/vuln/detail/CVE-2026-74582
- git.kernel.org/stable/c/142e287b3a25cfe909215177c23243e7fc5ae2b1
- github.com/advisories/GHSA-6g47-hqw2-hv2r
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 9h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 9h
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 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
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 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 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-74582 is "packet: use consistent hard_header_len in non-ring send paths", 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. EPSS 0.12% estimates the probability of exploitation in 30 days; neither replaces your asset context. 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.