Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-97599ieee802154: hwsim: serialize pib updates to fix double-free

Description

In the Linux kernel, the following vulnerability has been resolved: ieee802154: hwsim: serialize pib updates to fix double-free hwsim_update_pib() does an unserialized read-swap-free of phy->pib: pib_old = rtnl_dereference(phy->pib); ... rcu_assign_pointer(phy->pib, pib); kfree_rcu(pib_old, rcu); It assumes the RTNL is held, but ->set_channel is not always called under it: the mac802154 scan worker changes channels via drv_set_channel() without the RTNL. Such an update can race an RTNL-held one on the same phy; both read the same pib_old and both kfree_rcu() it, double-freeing the object. With SLUB percpu sheaves batching kfree_rcu(), this surfaces as a KASAN invalid-free in rcu_free_sheaf(). struct hwsim_phy has no lock for pib. Add one and make the swap atomic with rcu_replace_pointer() under it, dropping the misleading rtnl_dereference().

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 35 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

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

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (12 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 f25da51fdc381ca2863248c7060b3662632f0872 – < 8f44a61f816581c35c1974c8c1a3b3c2c49e96be
    • affected f25da51fdc381ca2863248c7060b3662632f0872 – < e3b4681197aa026bd2d79358de5a3d62b76b04b9
    • affected f25da51fdc381ca2863248c7060b3662632f0872 – < 9973b3a67a7592a780ea12b08334539a900deec1
    • affected f25da51fdc381ca2863248c7060b3662632f0872 – < d3b8f264ce09573aededd0a97dc41c8147797d8f
    • affected f25da51fdc381ca2863248c7060b3662632f0872 – < db6442deecb1f13aeaf4f9d77746ea7555630fb3
    • affected f25da51fdc381ca2863248c7060b3662632f0872 – < 979d5b8de8ed4e1f997aef12da5694b99be7b871
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .