Skip to main content
VulnerabilityPublished Updated

CVE-2026-46086: Linux kernel · net: bridge: use a stable FDB dst snapshot in RCU readers

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in df4601653201de21b487c3e7fffd464790cab808 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in df4601653201de21b487c3e7fffd464790cab808, c502fa9f094cb03d1d1685c71e2105ab359bc2b8, a6ae4511c07b91f597e461406c6330f0d4ff810e +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 960b589f86c74ce582922fcb996103271081f4de, < df4601653201de21b487c3e7fffd464790cab808
Fixed in
  • df4601653201de21b487c3e7fffd464790cab808
LinuxLinuxAffected
  • ≥ 960b589f86c74ce582922fcb996103271081f4de, < c502fa9f094cb03d1d1685c71e2105ab359bc2b8
Fixed in
  • c502fa9f094cb03d1d1685c71e2105ab359bc2b8
LinuxLinuxAffected
  • ≥ 960b589f86c74ce582922fcb996103271081f4de, < a6ae4511c07b91f597e461406c6330f0d4ff810e
Fixed in
  • a6ae4511c07b91f597e461406c6330f0d4ff810e
LinuxLinuxAffected
  • ≥ 960b589f86c74ce582922fcb996103271081f4de, < 5424e678f9b304e148cf5dcc047cffc7a56a3bb5
Fixed in
  • 5424e678f9b304e148cf5dcc047cffc7a56a3bb5
LinuxLinuxAffected
  • ≥ 960b589f86c74ce582922fcb996103271081f4de, < 1406c4e0ed1eaf8a29801ab1163d00fb7ee4359a
Fixed in
  • 1406c4e0ed1eaf8a29801ab1163d00fb7ee4359a
LinuxLinuxAffected
  • ≥ 960b589f86c74ce582922fcb996103271081f4de, < 81af4137a30c4c2dc694dea8cacb180bd66000ef
Fixed in
  • 81af4137a30c4c2dc694dea8cacb180bd66000ef

Description

In the Linux kernel, the following vulnerability has been resolved: net: bridge: use a stable FDB dst snapshot in RCU readers Local FDB entries can be rewritten in place by `fdb_delete_local()`, which updates `f->dst` to another port or to `NULL` while keeping the entry alive. Several bridge RCU readers inspect `f->dst`, including `br_fdb_fillbuf()` through the `brforward_read()` sysfs path. These readers currently load `f->dst` multiple times and can therefore observe inconsistent values across the check and later dereference. In `br_fdb_fillbuf()`, this means a concurrent local-FDB update can change `f->dst` after the NULL check and before the `port_no` dereference, leading to a NULL-ptr-deref. Fix this by taking a single `READ_ONCE()` snapshot of `f->dst` in each affected RCU reader and using that snapshot for the rest of the access sequence. Also publish the in-place `f->dst` updates in `fdb_delete_local()` with `WRITE_ONCE()` so the readers and writer use matching access patterns.

References

Community reviews

Loading reviews…