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-53269netfilter: synproxy: add mutex to guard hook reference counting

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: synproxy: add mutex to guard hook reference counting As the synproxy infrastructure register netfilter hooks on-demand when a user adds the first iptables target or nftables expression, if done concurrently they can race each other. Introduce a mutex to serialize the refcount control blocks access from both frontends. While a per namespace mutex might be more efficient, it is not needed for target/expression like SYNPROXY.

Timeline

  1. ID reserved

    By Linux

  2. · 16 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-53269, 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.12% · top 98% of all CVEs (16 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 ad49d86e07a497e834cb06f2b151dccd75f8e148 – < 0ec9ddc1bda261a2c57636c74c8b4e53000102c9
    • affected ad49d86e07a497e834cb06f2b151dccd75f8e148 – < 56ffbe3a08c01dcdb0d6adee9ce1e535bfb3b389
    • affected ad49d86e07a497e834cb06f2b151dccd75f8e148 – < debc57b83d5b323df74bf010c8d50fe26ad2ed6b
    • affected ad49d86e07a497e834cb06f2b151dccd75f8e148 – < 0f8ba5e4c53d2e4a536aa68140beda9fe59b2f88
    • affected ad49d86e07a497e834cb06f2b151dccd75f8e148 – < 640441348258220e78daed40528b85b8afcedab6
    • affected ad49d86e07a497e834cb06f2b151dccd75f8e148 – < aaf80701dc2f7a48fe543961e21f8ca3924d587c
    • affected ad49d86e07a497e834cb06f2b151dccd75f8e148 – < fbf0591275f50eae5733c3d7a8cd6c1e79933ffa
    • affected ad49d86e07a497e834cb06f2b151dccd75f8e148 – < 2fcba19caaeb2a33017459d3430f057967bb91b6
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.94 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .