Linux Kernel up to 6.1.52/6.4.15/6.5.2 PCI release_resource privilege escalation

Summaryinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.1.52/6.4.15/6.5.2. Affected is the function release_resource of the component PCI. The manipulation leads to an unknown weakness. This vulnerability is referenced as CVE-2023-53743. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.1.52/6.4.15/6.5.2. This issue affects the function release_resource of the component PCI. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: PCI: Free released resource after coalescing release_resource() doesn't actually free the resource or resource list entry so free the resource list entry to avoid a leak.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2023-53743 since 12/08/2025. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/22/2026).

The vulnerability scanner Nessus provides a plugin with the ID 277782 (Linux Distros Unpatched Vulnerability : CVE-2023-53743), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.1.53, 6.4.16 or 6.5.3 eliminates this vulnerability. Applying the patch 4443f3695d581ad1a55f2ef59259dcd0c52402b3/a076e73dd6e619729e1af8d0d802fe52ac5eb2b3/a08713b9d9031683b83b3ecf12bad40a1ca35211/8ec9c1d5d0a5a4744516adb483b97a238892f9d5 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.

The vulnerability is also documented in the databases at Tenable (277782), EUVD (EUVD-2023-60085) and CERT Bund (WID-SEC-2025-2756). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Google Container-Optimized OS
• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• Oracle Linux
• NetApp FAS
• NetApp AFF
• SUSE openSUSE
• RESF Rocky Linux
• Open Source Linux Kernel
• Microsoft Azure Linux

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 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.1.21
• 6.1.22
• 6.1.23
• 6.1.24
• 6.1.25
• 6.1.26
• 6.1.27
• 6.1.28
• 6.1.29
• 6.1.30
• 6.1.31
• 6.1.32
• 6.1.33
• 6.1.34
• 6.1.35
• 6.1.36
• 6.1.37
• 6.1.38
• 6.1.39
• 6.1.40
• 6.1.41
• 6.1.42
• 6.1.43
• 6.1.44
• 6.1.45
• 6.1.46
• 6.1.47
• 6.1.48
• 6.1.49
• 6.1.50
• 6.1.51
• 6.1.52
• 6.4.0
• 6.4.1
• 6.4.2
• 6.4.3
• 6.4.4
• 6.4.5
• 6.4.6
• 6.4.7
• 6.4.8
• 6.4.9
• 6.4.10
• 6.4.11
• 6.4.12
• 6.4.13
• 6.4.14
• 6.4.15
• 6.5.0
• 6.5.1
• 6.5.2

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion