Improper Locking Affecting reiserfs-kmp-default package, versions <6.4.0-150700.53.55.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.02% (8th 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-REISERFSKMPDEFAULT-17148071
  • published4 Jun 2026
  • disclosed3 Jun 2026

Introduced: 3 Jun 2026

NewCVE-2026-23357  (opens in a new tab)
CWE-667  (opens in a new tab)

How to fix?

Upgrade SLES:15.7 reiserfs-kmp-default to version 6.4.0-150700.53.55.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream reiserfs-kmp-default package and not the reiserfs-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:

can: mcp251x: fix deadlock in error path of mcp251x_open

The mcp251x_open() function call free_irq() in its error path with the mpc_lock mutex held. But if an interrupt already occurred the interrupt handler will be waiting for the mpc_lock and free_irq() will deadlock waiting for the handler to finish.

This issue is similar to the one fixed in commit 7dd9c26bd6cf ("can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open") but for the error path.

To solve this issue move the call to free_irq() after the lock is released. Setting priv-&gt;force_quit = 1 beforehand ensure that the IRQ handler will exit right away once it acquired the lock.

CVSS Base Scores

version 3.1