NULL Pointer Dereference Affecting ocfs2-kmp-default package, versions <6.4.0-150700.53.73.2


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.12% (3rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES157-OCFS2KMPDEFAULT-18207513
  • published22 Jul 2026
  • disclosed21 Jul 2026

Introduced: 21 Jul 2026

NewCVE-2026-46086  (opens in a new tab)
CWE-476  (opens in a new tab)

How to fix?

Upgrade SLES:15.7 ocfs2-kmp-default to version 6.4.0-150700.53.73.2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ocfs2-kmp-default package and not the ocfs2-kmp-default package as distributed by SLES. See How to fix? for SLES:15.7 relevant fixed versions and status.

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-&gt;dst to another port or to NULL while keeping the entry alive. Several bridge RCU readers inspect f-&gt;dst, including br_fdb_fillbuf() through the brforward_read() sysfs path.

These readers currently load f-&gt;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-&gt;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-&gt;dst in each affected RCU reader and using that snapshot for the rest of the access sequence. Also publish the in-place f-&gt;dst updates in fdb_delete_local() with WRITE_ONCE() so the readers and writer use matching access patterns.

CVSS Base Scores

version 3.1