Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-48931: configfs: fix a race in configfs_{,un}register_subsystem()

Noroxi assessment

Priority: Monitor (action score 18/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.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 3aadfd46858b1f64d4d6a0654b863e21aabff975, 40805099af11f68c5ca7dbcfacf455da8f99f622, 84ec758fb2daa236026506868c8796b0500c047d.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 3aadfd46858b1f64d4d6a0654b863e21aabff975, 40805099af11f68c5ca7dbcfacf455da8f99f622, 84ec758fb2daa236026506868c8796b0500c047d 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: configfs: fix a race in configfs_{,un}register_subsystem() When configfs_register_subsystem() or configfs_unregister_subsystem() is executing link_group() or unlink_group(), it is possible that two processes add or delete list concurrently. Some unfortunate interleavings of them can cause kernel panic. One of cases is: A --> B --> C --> D A <-- B <-- C <-- D delete list_head *B | delete list_head *C --------------------------------|----------------------------------- configfs_unregister_subsystem | configfs_unregister_subsystem unlink_group | unlink_group unlink_obj | unlink_obj list_del_init | list_del_init __list_del_entry | __list_del_entry __list_del | __list_del // next == C | next->prev = prev | | next->prev = prev prev->next = next | | // prev == B | prev->next = next Fix this by adding mutex when calling link_group() or unlink_group(), but parent configfs_subsystem is NULL when config_item is root. So I create a mutex configfs_subsystem_mutex.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Aug 22, 2024
Updated
Jun 17, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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-2022-48931

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

Running WordPress? Scan your site free with WP Lens

  • 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

Running WordPress? Scan your site free with WP Lens

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 kernel2.6.16 and later · before 4.9.304
  • linux linux kernel4.10 and later · before 4.14.269
  • linux linux kernel4.15 and later · before 4.19.232
  • linux linux kernel4.20 and later · before 5.4.182
  • linux linux kernel5.5 and later · before 5.10.103
  • linux linux kernel5.11 and later · before 5.15.26
  • linux linux kernel5.16 and later · before 5.16.12

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

    • 2.6.16affected
    • 7063fbf2261194f72ee75afca67b3b38b554b5fa and later · before 40805099af11f68c5ca7dbcfacf455da8f99f622affected · git
    • 7063fbf2261194f72ee75afca67b3b38b554b5fa and later · before d1654de19d42f513b6cfe955cc77e7f427e05a77affected · git
    • 7063fbf2261194f72ee75afca67b3b38b554b5fa and later · before a37024f7757c25550accdebf49e497ad6ae239feaffected · git
    • 7063fbf2261194f72ee75afca67b3b38b554b5fa and later · before b7e2b91fcb5c78c414e33dc8d50642e307ca0c5aaffected · git
    • 7063fbf2261194f72ee75afca67b3b38b554b5fa and later · before a7ab53d3c27dfe83bb594456b9f38a37796ec39baffected · git
    • 7063fbf2261194f72ee75afca67b3b38b554b5fa and later · before e7a66dd2687758718eddd79b542a95cf3aa488ccaffected · git
    • 7063fbf2261194f72ee75afca67b3b38b554b5fa and later · before 3aadfd46858b1f64d4d6a0654b863e21aabff975affected · git
    • 7063fbf2261194f72ee75afca67b3b38b554b5fa and later · before 84ec758fb2daa236026506868c8796b0500c047daffected · git
    • before 2.6.16not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.16.12-15.16.12-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-2022-48929Aug 22, 2024 · bpf: Fix crash due to out of bounds access into reg2btf_ids.
    22Monitor
  • ← EarlierCVE-2022-48930Aug 22, 2024 · RDMA/ib_srp: Fix a deadlock
    22Monitor
  • Later →CVE-2022-48932Aug 22, 2024 · net/mlx5: DR, Fix slab-out-of-bounds in mlx5_cmd_dr_create_fte
    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 Linux3aadfd46858b1f64d4d6a0654b863e21aabff975Vendor (CNA)
Linux Linux40805099af11f68c5ca7dbcfacf455da8f99f622Vendor (CNA)
Linux Linux84ec758fb2daa236026506868c8796b0500c047dVendor (CNA)
Linux Linuxa37024f7757c25550accdebf49e497ad6ae239feVendor (CNA)
Linux Linuxa7ab53d3c27dfe83bb594456b9f38a37796ec39bVendor (CNA)
Linux Linuxb7e2b91fcb5c78c414e33dc8d50642e307ca0c5aVendor (CNA)
Linux Linuxd1654de19d42f513b6cfe955cc77e7f427e05a77Vendor (CNA)
Linux Linuxe7a66dd2687758718eddd79b542a95cf3aa488ccVendor (CNA)
debian:linux5.16.12-1 · Debian:12Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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.
  • Special conditions such as timing or configuration are required.

If successful

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

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:H/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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

Show all references (7 more)

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

All records