Linux Kernel up to 6.2.7 ndlc_remove use after free

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.2.7. It has been classified as critical. The affected element is the function ndlc_remove. This manipulation causes use after free. This vulnerability is handled as CVE-2023-53106. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 6.2.7 and classified as critical. Affected by this vulnerability is the function ndlc_remove. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2023-53106 since 05/02/2025. The exploitation appears to be easy. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/10/2025).

Upgrading to version 4.14.311, 4.19.279, 5.4.238, 5.10.176, 5.15.104, 6.1.21 or 6.2.8 eliminates this vulnerability. Applying the patch 2156490c4b7cacda9a18ec99929940b8376dc0e3/3405eb641dafcc8b28d174784b203c1622c121bf/b0c202a8dc63008205a5d546559736507a9aae66/43aa468df246175207a7d5d7d6d31b231f15b49c/84dd9cc34014e3a3dcce0eb6d54b8a067e97676b/5e331022b448fbc5e76f24349cd0246844dcad25/f589e5b56c562d99ea74e05b1c3f0eab78aa17a3/5000fe6c27827a61d8250a7e4a1d26c3298ef4f6 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 4.14.310
• 4.19.278
• 5.4.237
• 5.10.175
• 5.15.103
• 6.1.0
• 6.1.1
• 6.1.2
• 6.1.3
• 6.1.4
• 6.1.5
• 6.1.6
• 6.1.7
• 6.1.8
• 6.1.9
• 6.1.10
• 6.1.11
• 6.1.12
• 6.1.13
• 6.1.14
• 6.1.15
• 6.1.16
• 6.1.17
• 6.1.18
• 6.1.19
• 6.1.20
• 6.2.0
• 6.2.1
• 6.2.2
• 6.2.3
• 6.2.4
• 6.2.5
• 6.2.6
• 6.2.7

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion