netlink: reset skb headers before unicast and multicast filtering
Summary
| CVE | CVE-2026-99211 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-28 11:17:42 UTC |
| Updated | 2026-10-30 13:21:53 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: netlink: reset skb headers before unicast and multicast filtering Socket filters can use SKF_NET_OFF and SKF_LL_OFF to read relative to an skb's network and MAC headers. Netlink producers may reserve headroom without resetting those headers, allowing a receiving socket's filter to read data before the initialized message. For example, IWPM HELLO replies are allocated with dev_alloc_skb(), which reserves NET_SKB_PAD bytes. An unprivileged NETLINK_RDMA user can attach a classic socket filter and disclose this headroom through the length of the delivered reply. The resets in netlink_dump() do not help because IWPM sends a separately allocated skb through netlink_unicast(). Reset both headers before running the receiver's filter in unicast and broadcast delivery, as is already done for dump skbs. This also covers other netlink producers that reserve headroom without changing their allocation or message-building code. |
Risk And Classification
EPSS: 0.001600000 probability, percentile 0.052220000 (date 2026-10-30)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected b1153f29ee07dc1a788964409255a4b4fae50b98 4123f8d2099863e2421187af9d87b45e8eebd867 git | Not specified |
| CNA | Linux | Linux | affected b1153f29ee07dc1a788964409255a4b4fae50b98 6ec7cc02458c6a1509377a7f2eec9c7b1a355b5e git | Not specified |
| CNA | Linux | Linux | affected b1153f29ee07dc1a788964409255a4b4fae50b98 ea0e0fc4c72f71bd6d8bf460bfe309b61c35b548 git | Not specified |
| CNA | Linux | Linux | affected b1153f29ee07dc1a788964409255a4b4fae50b98 c69db9e1f5cf886d4e3011313761a0f63a1d0da0 git | Not specified |
| CNA | Linux | Linux | affected b1153f29ee07dc1a788964409255a4b4fae50b98 06791594274f87c29f1a9f1961d700272716a49d git | Not specified |
| CNA | Linux | Linux | affected b1153f29ee07dc1a788964409255a4b4fae50b98 06935da5de83aa8b98841563894857e7d2f80e47 git | Not specified |
| CNA | Linux | Linux | affected b1153f29ee07dc1a788964409255a4b4fae50b98 8bf659bd54e1f00e34cf5244b1d289c506fa47c0 git | Not specified |
| CNA | Linux | Linux | affected 2.6.26 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.26 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.273 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.224 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.161 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.115 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.59 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.13 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/c69db9e1f5cf886d4e3011313761a0f63a1d0da0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/6ec7cc02458c6a1509377a7f2eec9c7b1a355b5e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/8bf659bd54e1f00e34cf5244b1d289c506fa47c0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ea0e0fc4c72f71bd6d8bf460bfe309b61c35b548 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/06791594274f87c29f1a9f1961d700272716a49d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/06935da5de83aa8b98841563894857e7d2f80e47 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/4123f8d2099863e2421187af9d87b45e8eebd867 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.