Skip to content
Noroxi
CVE-2025-71233· NVD / CVE Program· CNA Linux

PCI: endpoint: Avoid creating sub-groups asynchronously

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.13% (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 24a253c3aa6d9a2cde46158ce9782e023bfbf32d, 5f609b3bffd4207cf9f2c9b41e1978457a5a1ea9, 73cee890adafa2c219bb865356e08e7f82423fe5; azl3 kernel 6.6.126.1-1 on Azure Linux 3.0 6.6.130.1-1; cbl2 kernel 5.15.200.1-1 on CBL Mariner 2.0 5.15.202.1-1.

Low priority for now. Upgrade to Linux Linux 24a253c3aa6d9a2cde46158ce9782e023bfbf32d, 5f609b3bffd4207cf9f2c9b41e1978457a5a1ea9, 73cee890adafa2c219bb865356e08e7f82423fe5; azl3 kernel 6.6.126.1-1 on Azure Linux 3.0 6.6.130.1-1; cbl2 kernel 5.15.200.1-1 on CBL Mariner 2.0 5.15.202.1-1 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: PCI: endpoint: Avoid creating sub-groups asynchronously The asynchronous creation of sub-groups by a delayed work could lead to a NULL pointer dereference when the driver directory is removed before the work completes. The crash can be easily reproduced with the following commands: # cd /sys/kernel/config/pci_ep/functions/pci_epf_test # for i in {1..20}; do mkdir test && rmdir test; done BUG: kernel NULL pointer dereference, address: 0000000000000088 ... Call Trace: configfs_register_group+0x3d/0x190 pci_epf_cfs_work+0x41/0x110 process_one_work+0x18f/0x350 worker_thread+0x25a/0x3a0 Fix this issue by using configfs_add_default_group() API which does not have the deadlock problem as configfs_register_group() and does not require the delayed work handler. [mani: slightly reworded the description and added stable list]

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 18, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 2th percentile

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.1%

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-2025-71233

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.

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 kernel5.12 and later · before 5.15.201
  • linux linux kernel5.16 and later · before 6.1.164
  • linux linux kernel6.2 and later · before 6.6.127
  • linux linux kernel6.7 and later · before 6.12.72
  • linux linux kernel6.13 and later · before 6.18.11
  • linux linux kernel6.19 and later · before 6.19.1

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.12affected
    • e85a2d7837622bd99c96f5bbc7f972da90c285a2 and later · before fa9fb38f5fe9c80094c2138354d45cdc8d094d69affected · git
    • e85a2d7837622bd99c96f5bbc7f972da90c285a2 and later · before 5f609b3bffd4207cf9f2c9b41e1978457a5a1ea9affected · git
    • e85a2d7837622bd99c96f5bbc7f972da90c285a2 and later · before 8cb905eca73944089a0db01443c7628a9e87012daffected · git
    • e85a2d7837622bd99c96f5bbc7f972da90c285a2 and later · before d9af3cf58bb4c8d6dea4166011c780756b1138b5affected · git
    • e85a2d7837622bd99c96f5bbc7f972da90c285a2 and later · before 24a253c3aa6d9a2cde46158ce9782e023bfbf32daffected · git
    • e85a2d7837622bd99c96f5bbc7f972da90c285a2 and later · before 73cee890adafa2c219bb865356e08e7f82423fe5affected · git
    • e85a2d7837622bd99c96f5bbc7f972da90c285a2 and later · before 7c5c7d06bd1f86d2c3ebe62be903a4ba42db4d2caffected · git
    • before 5.12not affected · semver
    • 5.15.201 and later · up to and including 5.15.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.164-16.1.164-1
Debian:13linuxbefore 6.12.73-16.12.73-1
Debian:14linuxbefore 6.18.12-16.18.12-1
openSUSE:Tumbleweedkernel-sourcebefore 6.19.8-1.16.19.8-1.1

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-71230Feb 18, 2026 · hfs: ensure sb->s_fs_info is always cleaned up
    22Monitor
  • ← EarlierCVE-2025-71231Feb 18, 2026 · crypto: iaa - Fix out-of-bounds index in find_empty_iaa_compression_mode
    28Monitor
  • Later →CVE-2025-71237Feb 18, 2026 · nilfs2: Fix potential block overflow that cause system hang
    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 Linux24a253c3aa6d9a2cde46158ce9782e023bfbf32dVendor (CNA)
Linux Linux5f609b3bffd4207cf9f2c9b41e1978457a5a1ea9Vendor (CNA)
Linux Linux73cee890adafa2c219bb865356e08e7f82423fe5Vendor (CNA)
Linux Linux7c5c7d06bd1f86d2c3ebe62be903a4ba42db4d2cVendor (CNA)
Linux Linux8cb905eca73944089a0db01443c7628a9e87012dVendor (CNA)
Linux Linuxd9af3cf58bb4c8d6dea4166011c780756b1138b5Vendor (CNA)
Linux Linuxfa9fb38f5fe9c80094c2138354d45cdc8d094d69Vendor (CNA)
azl3 kernel 6.6.126.1-1 on Azure Linux 3.06.6.130.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.200.1-1 on CBL Mariner 2.05.15.202.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.164-1 · Debian:12Package registry (OSV)
opensuse:kernel-source6.19.8-1.1 · openSUSE:TumbleweedPackage 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.

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

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. Fix✗ → ✓

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

References

All records