NVD / CVE Program· CNA Linux

CVE-2023-53106: nfc: st-nci: Fix use after free bug in ndlc_remove due to race condition

Noroxi assessment

Priority: Monitor (action score 31/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.20% (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 2156490c4b7cacda9a18ec99929940b8376dc0e3, 3405eb641dafcc8b28d174784b203c1622c121bf, 43aa468df246175207a7d5d7d6d31b231f15b49c.

Low priority for now. Upgrade to Linux Linux 2156490c4b7cacda9a18ec99929940b8376dc0e3, 3405eb641dafcc8b28d174784b203c1622c121bf, 43aa468df246175207a7d5d7d6d31b231f15b49c 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: nfc: st-nci: Fix use after free bug in ndlc_remove due to race condition This bug influences both st_nci_i2c_remove and st_nci_spi_remove. Take st_nci_i2c_remove as an example. In st_nci_i2c_probe, it called ndlc_probe and bound &ndlc->sm_work with llt_ndlc_sm_work. When it calls ndlc_recv or timeout handler, it will finally call schedule_work to start the work. When we call st_nci_i2c_remove to remove the driver, there may be a sequence as follows: Fix it by finishing the work before cleanup in ndlc_remove CPU0 CPU1 |llt_ndlc_sm_work st_nci_i2c_remove | ndlc_remove | st_nci_remove | nci_free_device| kfree(ndev) | //free ndlc->ndev | |llt_ndlc_rcv_queue |nci_recv_frame |//use ndlc->ndev

HighCVSS 7.8 · v3.1—No exploit Fix available

BDU:2026-03856

Published: May 2, 2025
Updated: Jun 17, 2026
EPSS: 0.2% · 10th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

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.

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.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

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

linux linux kernel3.17 and later · before 4.14.311
linux linux kernel4.15 and later · before 4.19.279
linux linux kernel4.20 and later · before 5.4.238
linux linux kernel5.5 and later · before 5.10.176
linux linux kernel5.11 and later · before 5.15.104
linux linux kernel5.16 and later · before 6.1.21
linux linux kernel6.2 and later · before 6.2.8
linux linux kernel6.3

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
- 3.17affected
- 35630df68d6030daf12dde12ed07bbe26324e6ac and later · before 2156490c4b7cacda9a18ec99929940b8376dc0e3affected · git
- 35630df68d6030daf12dde12ed07bbe26324e6ac and later · before 3405eb641dafcc8b28d174784b203c1622c121bfaffected · git
- 35630df68d6030daf12dde12ed07bbe26324e6ac and later · before b0c202a8dc63008205a5d546559736507a9aae66affected · git
- 35630df68d6030daf12dde12ed07bbe26324e6ac and later · before 43aa468df246175207a7d5d7d6d31b231f15b49caffected · git
- 35630df68d6030daf12dde12ed07bbe26324e6ac and later · before 84dd9cc34014e3a3dcce0eb6d54b8a067e97676baffected · git
- 35630df68d6030daf12dde12ed07bbe26324e6ac and later · before 5e331022b448fbc5e76f24349cd0246844dcad25affected · git
- 35630df68d6030daf12dde12ed07bbe26324e6ac and later · before f589e5b56c562d99ea74e05b1c3f0eab78aa17a3affected · git
- 35630df68d6030daf12dde12ed07bbe26324e6ac and later · before 5000fe6c27827a61d8250a7e4a1d26c3298ef4f6affected · git
- before 3.17not affected · semver

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.25-1	6.1.25-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-53098May 2, 2025 · media: rc: gpio-ir-recv: add remove function
22Monitor
← EarlierCVE-2023-53099May 2, 2025 · firmware: xilinx: don't make a sleepable memory allocation from an atomic context
22Monitor
Later →CVE-2023-53117May 2, 2025 · fs: prevent out-of-bounds array speculation when closing a file descriptor
28Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
Linux Linux	2156490c4b7cacda9a18ec99929940b8376dc0e3	Vendor (CNA)
Linux Linux	3405eb641dafcc8b28d174784b203c1622c121bf	Vendor (CNA)
Linux Linux	43aa468df246175207a7d5d7d6d31b231f15b49c	Vendor (CNA)
Linux Linux	5000fe6c27827a61d8250a7e4a1d26c3298ef4f6	Vendor (CNA)
Linux Linux	5e331022b448fbc5e76f24349cd0246844dcad25	Vendor (CNA)
Linux Linux	84dd9cc34014e3a3dcce0eb6d54b8a067e97676b	Vendor (CNA)
Linux Linux	b0c202a8dc63008205a5d546559736507a9aae66	Vendor (CNA)
Linux Linux	f589e5b56c562d99ea74e05b1c3f0eab78aa17a3	Vendor (CNA)
debian:linux	6.1.25-1 · Debian:12	Package 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: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

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

Fix✗ → ✓Sep 28, 2026, 10:08 PM UTC

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

References

git.kernel.org/stable/c/2156490c4b7cacda9a18ec99929940b8376dc0e3

Show all references (7 more)

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

All records