Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2026-99211

netlink: reset skb headers before unicast and multicast filtering

Not scoredEPSS 0.17%
Published
Updated
Reserved
Assigned by
Linux

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.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (5 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected b1153f29ee07dc1a788964409255a4b4fae50b98 – < 4123f8d2099863e2421187af9d87b45e8eebd867
    • affected b1153f29ee07dc1a788964409255a4b4fae50b98 – < 6ec7cc02458c6a1509377a7f2eec9c7b1a355b5e
    • affected b1153f29ee07dc1a788964409255a4b4fae50b98 – < ea0e0fc4c72f71bd6d8bf460bfe309b61c35b548
    • affected b1153f29ee07dc1a788964409255a4b4fae50b98 – < c69db9e1f5cf886d4e3011313761a0f63a1d0da0
    • affected b1153f29ee07dc1a788964409255a4b4fae50b98 – < 06791594274f87c29f1a9f1961d700272716a49d
    • affected b1153f29ee07dc1a788964409255a4b4fae50b98 – < 06935da5de83aa8b98841563894857e7d2f80e47
    • affected b1153f29ee07dc1a788964409255a4b4fae50b98 – < 8bf659bd54e1f00e34cf5244b1d289c506fa47c0
  • Linux · Linux

    • affected 2.6.26
    • unaffected < 2.6.26
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.59 – ≤ 6.18.*
    • unaffected 7.2.13 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References (7)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99211 badge
[![CVE-2026-99211](https://trackcve.app/badge/CVE-2026-99211.svg)](https://trackcve.app/cve/CVE-2026-99211)

Record last updated .