Linux Kernel up to 6.12.107/6.18.48/7.1.12 selinux perm_read heap-based overflow

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.
9.5$5k-$25k1.40

Summaryinfo

A vulnerability classified as very critical was found in Linux Kernel up to 6.12.107/6.18.48/7.1.12. This affects the function perm_read of the component selinux. Executing a manipulation can lead to heap-based overflow. This vulnerability is handled as CVE-2026-80755. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.107/6.18.48/7.1.12. It has been declared as very critical. This vulnerability affects the function perm_read of the component selinux. The manipulation with an unknown input leads to a heap-based overflow vulnerability. The CWE definition for the vulnerability is CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: selinux: reject a permission value exceeding the class permission count perm_read() bounds a permission value by SEL_VEC_MAX but never by the nprim of the owning class or common, which is taken verbatim from the policy image. security_get_permissions() then writes perms[value - 1] into an nprim-sized kcalloc() array, so a class declaring fewer permissions than its largest permission value drives an out-of-bounds heap write. The top-level symbol tables are validated this way; the nested per-class permission table is not. Reject a permission whose value exceeds nprim, which is already set when perm_read() runs. Well-formed policies are unaffected. [PM: tweak comment for line length]

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-80755 since 08/26/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 09/03/2026).

Upgrading to version 6.12.108, 6.18.49 or 7.1.13 eliminates this vulnerability. Applying the patch 6c2ab7c4549f4f2305848df834e784651dbf1676/dfc59a062c386d3d4415ecdab781065a645f33cc/a7f3d4f22d920dc3c7d75f02ece0f7bf2c58437e/d14b5d0e97fccd27974fedc03b903408872907fd is able to eliminate this problem.

Once again VulDB remains the best source for 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: 9.9
VulDB Meta Temp Score: 9.5

VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Heap-based overflow
CWE: CWE-122 / CWE-119
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 6.12.108/6.18.49/7.1.13
Patch: 6c2ab7c4549f4f2305848df834e784651dbf1676/dfc59a062c386d3d4415ecdab781065a645f33cc/a7f3d4f22d920dc3c7d75f02ece0f7bf2c58437e/d14b5d0e97fccd27974fedc03b903408872907fd

Timelineinfo

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

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80755 (🔒)
GCVE (CVE): GCVE-0-2026-80755
GCVE (VulDB): GCVE-100-398356

Entryinfo

Created: 09/03/2026 11:00
Changes: 09/03/2026 11:00 (59)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!