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-45897netfilter: nft_counter: serialize reset with spinlock

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_counter: serialize reset with spinlock Add a global static spinlock to serialize counter fetch+reset operations, preventing concurrent dump-and-reset from underrunning values. The lock is taken before fetching the total so that two parallel resets cannot both read the same counter values and then both subtract them. A global lock is used for simplicity since resets are infrequent. If this becomes a bottleneck, it can be replaced with a per-net lock later.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 5 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-45897, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected fb1adb05ea87b6149e65a31e511756c4f470d0cd – < e13194e60217db02c2e7202375d9e5951267d87b
    • affected f123293db16dcd0cd81b246ae60e6362f0025d0a – < de6601f1374fab124cd9276df6671f64d940ceb4
    • affected 3cb03edb4de33fd04c4ea55f47397b96a8657c53 – < 48cf7918d10c66cb6b05226fa3fa5daf0c891089
    • affected 3cb03edb4de33fd04c4ea55f47397b96a8657c53 – < cd968dcdec6aee79a2d399e4f6e0eca63c3b45e1
    • affected 3cb03edb4de33fd04c4ea55f47397b96a8657c53 – < 0cdc6d5a26f2d1f7f15a43526841b679445c32e2
    • affected 3cb03edb4de33fd04c4ea55f47397b96a8657c53 – < 779c60a5190c42689534172f4b49e927c9959e4e
    • affected 6.1.107 – < 6.1.188
    • affected 6.6.48 – < 6.6.157
  • Linux · Linux

    • affected 6.7
    • unaffected < 6.7
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 6.19.4 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .