CVE-2026-46086

net: bridge: use a stable FDB dst snapshot in RCU readers

MEDIUM
5.5
CVSS Score
Published: May 27, 2026 at 12:58 PM UTC
Updated: October 15, 2026 at 02:19 AM UTC
4 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSiplus S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.14.1 ≤ v < 5.10.2595.11 ≤ v < 5.15.2105.16 ≤ v < 6.1.1766.13 ≤ v < 6.18.276.19 ≤ v < 7.0.46.2 ≤ v < 6.6.1406.7 ≤ v < 6.12.863.143.14 rc33.14 rc43.14 rc53.14 rc63.14 rc73.14 rc8960b589f86c74ce582922fcb996103271081f4de
Vendor states this is fixed in 0b9e4bbfb7c949151e3acd44ed4aa33614d2e110 (fixed)
Vendor states this is fixed in 1406c4e0ed1eaf8a29801ab1163d00fb7ee4359a (fixed)
Vendor states this is fixed in 5424e678f9b304e148cf5dcc047cffc7a56a3bb5 (fixed)
Vendor states this is fixed in 81af4137a30c4c2dc694dea8cacb180bd66000ef (fixed)
Vendor states this is fixed in 9a2d9d4e657b23dc21f24cf139e3aeff0b61341f (fixed)
Vendor states this is fixed in a6ae4511c07b91f597e461406c6330f0d4ff810e (fixed)
Vendor states this is fixed in c502fa9f094cb03d1d1685c71e2105ab359bc2b8 (fixed)
Vendor states this is fixed in df4601653201de21b487c3e7fffd464790cab808 (fixed)
Vendor states this is fixed in 3.14 (unaffected)
Vendor states this is fixed in 5.10.259 (unaffected)
Vendor states this is fixed in 5.15.210 (unaffected)
Vendor states this is fixed in 6.1.176 (unaffected)
Vendor states this is fixed in 6.12.86 (unaffected)
Vendor states this is fixed in 6.18.27 (unaffected)
Vendor states this is fixed in 6.6.140 (unaffected)
Vendor states this is fixed in 7.0.4 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusUNDERGOING ANALYSIS
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card