Linux Kernel up to 7.1.4 sched copy_from_user memory corruption

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.
8.4$0-$5k0.48

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.1.4. It has been rated as very critical. Affected by this vulnerability is the function copy_from_user of the component sched. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2026-72181. The attack is only possible with local access. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as very critical, was found in Linux Kernel up to 7.1.4. This affects the function copy_from_user of the component sched. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: mips: sched: Fix CPUMASK_OFFSTACK memory corruption This patch addresses a critical memory management flaw. When CONFIG_CPUMASK_OFFSTACK is enabled, cpumask_var_t is a pointer. Consequently, sizeof(new_mask) evaluates to the pointer size, causing copy_from_user() to clobber the mask pointer. Furthermore, the old logic performed copy_from_user() before allocating the mask. Fix this by allocating new_mask first. To handle variable-sized user masks correctly, use cpumask_size() to truncate overly large user masks or pad undersized masks with zeros before copying the data directly into the allocated buffer.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-72181 since 08/09/2026. The exploitability is told to be easy. An attack has to be approached locally. 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 08/15/2026).

Upgrading to version 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 or 7.2-rc1 eliminates this vulnerability. Applying the patch d20ee42f8226607b5693b2bc2f115ca2d270221a/15ba8053fe4162c933855f1676fb321cdb6251c7/3446ffb5d03c36f9ce88ede7ca5be319a2968d96/87a56c1e8e36d06ebe8640432f911538ded7827d/1caee6e084a96ada94658f261ced377d85af3f03/a1dd41d00c57efb1fbc6f361c5f48c9d00cca51c/98e37db4a34d3af3fb2f4648295c25b5e40b20e3 is able to eliminate this problem.

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

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.4

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

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.15.212/6.1.178/6.6.145/6.12.97/6.18.40/7.1.5/7.2-rc1
Patch: d20ee42f8226607b5693b2bc2f115ca2d270221a/15ba8053fe4162c933855f1676fb321cdb6251c7/3446ffb5d03c36f9ce88ede7ca5be319a2968d96/87a56c1e8e36d06ebe8640432f911538ded7827d/1caee6e084a96ada94658f261ced377d85af3f03/a1dd41d00c57efb1fbc6f361c5f48c9d00cca51c/98e37db4a34d3af3fb2f4648295c25b5e40b20e3

Timelineinfo

08/09/2026 CVE reserved
08/15/2026 +6 days Advisory disclosed
08/15/2026 +0 days VulDB entry created
08/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-72181 (🔒)
GCVE (CVE): GCVE-0-2026-72181
GCVE (VulDB): GCVE-100-390621

Entryinfo

Created: 08/15/2026 13:23
Changes: 08/15/2026 13:23 (59)
Complete: 🔍
Cache ID: 216::103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!