Linux Kernel up to 7.2-rc3 spufs spufs_mem_mmap_access out-of-bounds

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.
6.0$0-$5k0.00+

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.2-rc3. It has been rated as critical. This impacts the function spufs_mem_mmap_access of the component spufs. Performing a manipulation results in out-of-bounds. This vulnerability is identified as CVE-2026-68474. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.2-rc3. It has been classified as critical. This affects the function spufs_mem_mmap_access of the component spufs. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended 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: powerpc/spufs: fix out-of-bounds access in spufs_mem_mmap_access() spufs_mem_mmap_access() computes the local store offset as address - vma->vm_start, but bounds-checks it against vma->vm_end instead of the local store size. On 64-bit, offset is always well below vma->vm_end, so the clamp never fires and len stays unbounded against the LS_SIZE buffer returned by ctx->ops->get_ls(). Reject offsets at or beyond LS_SIZE and clamp len to the remaining space, mirroring the guard already used by spufs_mem_mmap_fault() and spufs_ps_fault().

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-68474 since 07/30/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. 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.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 or 7.2-rc4 eliminates this vulnerability. Applying the patch aa7aa8ba40c089762d821e3987aaae19e1f5705c/d479a7711f8ff127946467b910d947bd971b94ed/9d3569bfdceda69d5ffd5148901e57b69954d9ef/d97a8f3668949a8a9d1f6202f8c53446f2d89aa7/913feef74354c653f10ecd4631df7618a95c49c2/3c1e92f75e11a11492b8cb901fceeb9f16ae6415/4efa313b15925bdd864784865d6585174979294b/47b87f469a35b5ffc81c16eee6b13a9b6c8d55c6 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: 6.3
VulDB Meta Temp Score: 6.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / 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 5.10.261/5.15.212/6.1.178/6.6.145/6.12.97/6.18.40/7.1.5/7.2-rc4
Patch: aa7aa8ba40c089762d821e3987aaae19e1f5705c/d479a7711f8ff127946467b910d947bd971b94ed/9d3569bfdceda69d5ffd5148901e57b69954d9ef/d97a8f3668949a8a9d1f6202f8c53446f2d89aa7/913feef74354c653f10ecd4631df7618a95c49c2/3c1e92f75e11a11492b8cb901fceeb9f16ae6415/4efa313b15925bdd864784865d6585174979294b/47b87f469a35b5ffc81c16eee6b13a9b6c8d55c6

Timelineinfo

07/30/2026 CVE reserved
08/15/2026 +16 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-68474 (🔒)
GCVE (CVE): GCVE-0-2026-68474
GCVE (VulDB): GCVE-100-390201

Entryinfo

Created: 08/15/2026 08:18
Changes: 08/15/2026 08:18 (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.

Do you know our Splunk app?

Download it now for free!