Linux Kernel up to 7.2.0 pn533 pn53x_common_clean memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.41

Summaryinfo

A vulnerability classified as critical has been found in Linux Kernel up to 7.2.0. Impacted is the function pn53x_common_clean of the component pn533. The manipulation leads to memory leak. This vulnerability is documented as CVE-2026-80797. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.2.0. It has been rated as critical. This issue affects the function pn53x_common_clean of the component pn533. The manipulation with an unknown input leads to a memory leak vulnerability. Using CWE to declare the problem leads to CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: purge fragmented skbs during cleanup pn53x_common_clean() purges resp_q before freeing the common PN533 state, but it leaves fragment_skb untouched. The fragmentation helpers queue transmit fragments there while sending large initiator or target-mode frames, and those skbs remain owned by the driver until they are sent or discarded. If the device is removed while fragments are still queued, the common cleanup path frees the PN533 state without releasing the queued fragment skbs, leaking them. Purge fragment_skb during cleanup alongside resp_q.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-80797 since 08/26/2026. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. 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 09/04/2026). MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, 6.18.47, 7.1.11, 7.2.1 or 7.3-rc1 eliminates this vulnerability. Applying the patch 130b5ad4492f8e53d0398ee3af2b0e2388504d11/9319c3c4962efc8697246b563ea31c6d47f085aa/d63e85c5d5555fe6aa65155d3a09452597e163c3/4a52ec2457ff8c26206fcc20fa1972cc35a678c4/e169277281373818ae1cedf976aa1e99118fb77d/2f5d093194ec24d7c29b91bf7df014924e0f4ea1/e7ed2ea5590fbe2d3be39ee4fb0c758a12e31d0c/e95beff58b38c871c557bf84e528408283c2c0ad/5718fc62198c38c2de5316020a90506f9e75e0bb is able to eliminate this problem.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.267/5.15.218/6.1.185/6.6.154/6.12.106/6.18.47/7.1.11/7.2.1/7.3-rc1
Patch: 130b5ad4492f8e53d0398ee3af2b0e2388504d11/9319c3c4962efc8697246b563ea31c6d47f085aa/d63e85c5d5555fe6aa65155d3a09452597e163c3/4a52ec2457ff8c26206fcc20fa1972cc35a678c4/e169277281373818ae1cedf976aa1e99118fb77d/2f5d093194ec24d7c29b91bf7df014924e0f4ea1/e7ed2ea5590fbe2d3be39ee4fb0c758a12e31d0c/e95beff58b38c871c557bf84e528408283c2c0ad/5718fc62198c38c2de5316020a90506f9e75e0bb

Timelineinfo

08/26/2026 CVE reserved
09/04/2026 +9 days Advisory disclosed
09/04/2026 +0 days VulDB entry created
09/04/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80797 (🔒)
GCVE (CVE): GCVE-0-2026-80797
GCVE (VulDB): GCVE-100-399041

Entryinfo

Created: 09/04/2026 19:02
Changes: 09/04/2026 19:02 (59)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!