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-72323ipv4: igmp: Fix potential UAF in igmp_gq_start_timer()

Description

In the Linux kernel, the following vulnerability has been resolved: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() A race condition exists between device teardown (inetdev_destroy) and incoming IGMP query processing (igmp_rcv), leading to a Use-After-Free in the IGMP timer callback. During device destruction, inetdev_destroy() drops the primary reference to in_device, which can drop its refcount to 0. The actual freeing of in_device memory is deferred via RCU (using call_rcu()). Concurrently, igmp_rcv() runs under RCU read lock and obtains the in_device pointer. Because the memory is RCU-protected, CPU-0 can safely dereference in_device even if its refcount has hit 0. However, if CPU-0 calls igmp_gq_start_timer() and re-arms the timer, it attempts to acquire a reference using in_dev_hold(). This increments the refcount from 0 to 1, triggering a "refcount_t: addition on 0" warning. Since the in_device memory is still scheduled to be freed after the RCU grace period (as the free callback does not check the refcount again), the device is freed while the timer is still armed. When the timer expires, it accesses the freed memory, causing a kernel panic. Fix this by using refcount_inc_not_zero() (via a new helper in_dev_hold_safe()) to prevent acquiring a reference if the device is already being destroyed. If the refcount is 0, we do not arm the timer. A similar issue in IPv6 MLD is fixed in a subsequent patch.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 months 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

CVSS scores of CVE-2026-72323, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.72% · top 45% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7265c747eec415ca3109a6a14a419f7ae433b780
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d107b4c4f8274763b7ea5ab05d45cef78e4b81ba
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 74b301f7f197517016befb5f5dfab01f7bc64be5
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 40a1e998cb266ed4cb529a0bb4fee2b0ba732702
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 165258303357e54b75fc19b341ae2a2b7c9e3910
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 75e984fe0cb9e7fbde0c8ee838c61ce8573d3ea3
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8d4394ffa40508e0de72f464af351f6ca6a6cdc3
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7b19c0f81ed1fdaec6bc522569be367199a9edf3
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.269 – ≤ 5.10.*
    • unaffected 5.15.220 – ≤ 5.15.*
    • unaffected 6.1.187 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .