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-97901genetlink: pin family module during policy dump

Description

In the Linux kernel, the following vulnerability has been resolved: genetlink: pin family module during policy dump The generic netlink controller's policy dump keeps pointers to the target family's operation and policy tables in its callback state. A dump may be split across multiple skbs and remain pending after the initial request. Netlink pins the module which owns the dump callback, but in this case that is the controller's owner rather than the target family's owner. The target family can consequently be unregistered and its module unloaded while a policy dump is pending. Advancing the dump then dereferences policy memory from the unloaded module. Take a reference to the target family's module when the dump starts. Drop it from the error and done paths. This matches the lifetime for which the dump context retains the family and policy pointers.

Timeline

  1. ID reserved

    By Linux

  2. 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.22% · top 88% of all CVEs (13 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 d07dcf9aadd6b2842b439e8668ff7ea2873f28d7 – < 7ee2c0f82354da9bae04b14e0e5b2037d2de48a7
    • affected d07dcf9aadd6b2842b439e8668ff7ea2873f28d7 – < 7f71414c206a0e2babf4ec2756c0d15776c5dfd2
    • affected d07dcf9aadd6b2842b439e8668ff7ea2873f28d7 – < ad01ec35360e803670168d63a856629d6aeaec48
    • affected d07dcf9aadd6b2842b439e8668ff7ea2873f28d7 – < 1a345d95e59a99e25404138b5a1ec2edcb03269f
    • affected d07dcf9aadd6b2842b439e8668ff7ea2873f28d7 – < 6e4d746e55c83c240cffce92356763d16b236af5
    • affected d07dcf9aadd6b2842b439e8668ff7ea2873f28d7 – < 508387ad95ef9c13aa6431678c39763e882da2dc
    • affected d07dcf9aadd6b2842b439e8668ff7ea2873f28d7 – < 6d8e653fcf1c90310797eeba8e5fafe9ccc3de9e
    • affected d07dcf9aadd6b2842b439e8668ff7ea2873f28d7 – < 6a1094c34d176827b2b173e163dcc964a13af93f
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .