Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52982: fscache: Use wait_on_bit() to wait for the freeing of relinquished volume

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3be069f42a7b79d3149194f21cdf24bf23864cac, 8226e37d82f43657da34dd770e2b38f20242ada7.

Low priority for now. Upgrade to Linux Linux 3be069f42a7b79d3149194f21cdf24bf23864cac, 8226e37d82f43657da34dd770e2b38f20242ada7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: fscache: Use wait_on_bit() to wait for the freeing of relinquished volume The freeing of relinquished volume will wake up the pending volume acquisition by using wake_up_bit(), however it is mismatched with wait_var_event() used in fscache_wait_on_volume_collision() and it will never wake up the waiter in the wait-queue because these two functions operate on different wait-queues. According to the implementation in fscache_wait_on_volume_collision(), if the wake-up of pending acquisition is delayed longer than 20 seconds (e.g., due to the delay of on-demand fd closing), the first wait_var_event_timeout() will timeout and the following wait_var_event() will hang forever as shown below: FS-Cache: Potential volume collision new=00000024 old=00000022 ...... INFO: task mount:1148 blocked for more than 122 seconds. Not tainted 6.1.0-rc6+ #1 task:mount state:D stack:0 pid:1148 ppid:1 Call Trace: <TASK> __schedule+0x2f6/0xb80 schedule+0x67/0xe0 fscache_wait_on_volume_collision.cold+0x80/0x82 __fscache_acquire_volume+0x40d/0x4e0 erofs_fscache_register_volume+0x51/0xe0 [erofs] erofs_fscache_register_fs+0x19c/0x240 [erofs] erofs_fc_fill_super+0x746/0xaf0 [erofs] vfs_get_super+0x7d/0x100 get_tree_nodev+0x16/0x20 erofs_fc_get_tree+0x20/0x30 [erofs] vfs_get_tree+0x24/0xb0 path_mount+0x2fa/0xa90 do_mount+0x7c/0xa0 __x64_sys_mount+0x8b/0xe0 do_syscall_64+0x30/0x60 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Considering that wake_up_bit() is more selective, so fix it by using wait_on_bit() instead of wait_var_event() to wait for the freeing of relinquished volume. In addition because waitqueue_active() is used in wake_up_bit() and clear_bit() doesn't imply any memory barrier, use clear_and_wake_up_bit() to add the missing memory barrier between cursor->flags and waitqueue_active().

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Mar 27, 2025
Updated
Nov 5, 2026
EPSS
0.2% · 13th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-52982

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.17 and later · before 6.1.11
  • linux linux kernel6.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.17affected
    • 62ab63352350e881ae693a8236b35d7d0516c78b and later · before 3be069f42a7b79d3149194f21cdf24bf23864cacaffected · git
    • 62ab63352350e881ae693a8236b35d7d0516c78b and later · before 8226e37d82f43657da34dd770e2b38f20242ada7affected · git
    • before 5.17not affected · semver
    • 6.1.11 and later · up to and including 6.1.*not affected · semver
    • 6.2 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.11-16.1.11-1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-64kbbefore 5.14.21-150500.55.103.15.14.21-150500.55.103.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-docsbefore 5.14.21-150500.55.103.15.14.21-150500.55.103.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-obs-buildbefore 5.14.21-150500.55.103.15.14.21-150500.55.103.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-symsbefore 5.14.21-150500.55.103.15.14.21-150500.55.103.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_26before 1-150500.11.3.11-150500.11.3.1
SUSE:Linux Enterprise Micro 5.5kernel-defaultbefore 5.14.21-150500.55.103.15.14.21-150500.55.103.1
SUSE:Linux Enterprise Micro 5.5kernel-default-basebefore 5.14.21-150500.55.103.1.150500.6.49.15.14.21-150500.55.103.1.150500.6.49.1
SUSE:Linux Enterprise Micro 5.5kernel-rtbefore 5.14.21-150500.13.94.15.14.21-150500.13.94.1
SUSE:Linux Enterprise Micro 5.5kernel-sourcebefore 5.14.21-150500.55.103.15.14.21-150500.55.103.1
SUSE:Linux Enterprise Micro 5.5kernel-source-rtbefore 5.14.21-150500.13.94.15.14.21-150500.13.94.1
SUSE:Linux Enterprise Server 15 SP5-LTSSkernel-zfcpdumpbefore 5.14.21-150500.55.103.15.14.21-150500.55.103.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-52942Mar 27, 2025 · cgroup/cpuset: Fix wrong check in update_parent_subparts_cpumask()
    22Monitor
  • ← EarlierCVE-2023-52981Mar 27, 2025 · drm/i915: Fix request ref counting during error capture & debugfs dump
    22Monitor
  • Later →CVE-2023-52986Mar 27, 2025 · bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3be069f42a7b79d3149194f21cdf24bf23864cacVendor (CNA)
Linux Linux8226e37d82f43657da34dd770e2b38f20242ada7Vendor (CNA)
debian:linux6.1.11-1 · Debian:12Package registry (OSV)
suse:kernel-64kb5.14.21-150500.55.103.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSPackage registry (OSV)
suse:kernel-default5.14.21-150500.55.103.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-default-base5.14.21-150500.55.103.1.150500.6.49.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-docs5.14.21-150500.55.103.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP5_Update_261-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5Package registry (OSV)
suse:kernel-obs-build5.14.21-150500.55.103.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSPackage registry (OSV)
suse:kernel-rt5.14.21-150500.13.94.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-source5.14.21-150500.55.103.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-source-rt5.14.21-150500.13.94.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-syms5.14.21-150500.55.103.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSPackage registry (OSV)
suse:kernel-zfcpdump5.14.21-150500.55.103.1 · SUSE:Linux Enterprise Server 15 SP5-LTSSPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records