In the Linux kernel, the following vulnerability has been resolved: of: reserved_mem: avoid post-init UAF when alloc_reserved_mem_array() fails The… (CVE-2026-74352)
A use-after-free vulnerability in the Linux kernel's reserved memory handling was resolved. The issue occurs when alloc_reserved_mem_array() fails but the global pointer reserved_mem still references freed memory, leading to potential dereferencing of freed memory via of_reserved_mem_lookup(). The fix resets reserved_mem_count to 0 upon failure to prevent this condition.
AI Analysis
Technical Summary
The Linux kernel had a use-after-free vulnerability in the reserved memory subsystem. Specifically, if alloc_reserved_mem_array() fails, the global pointer reserved_mem continues to reference reserved_mem_array located in __initdata, which has been freed. Since of_reserved_mem_lookup() is available for use after initialization, it could dereference this freed memory, causing a use-after-free condition. The vulnerability was addressed by resetting reserved_mem_count to 0 when alloc_reserved_mem_array() fails, preventing access to freed memory.
Potential Impact
This vulnerability could lead to use-after-free conditions in the kernel, potentially causing system instability or crashes. No information about exploitation in the wild or privilege escalation is provided.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to reset reserved_mem_count to 0 when alloc_reserved_mem_array() fails, preventing use-after-free. Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; check the Linux kernel vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: of: reserved_mem: avoid post-init UAF when alloc_reserved_mem_array() fails The… (CVE-2026-74352)
Description
A use-after-free vulnerability in the Linux kernel's reserved memory handling was resolved. The issue occurs when alloc_reserved_mem_array() fails but the global pointer reserved_mem still references freed memory, leading to potential dereferencing of freed memory via of_reserved_mem_lookup(). The fix resets reserved_mem_count to 0 upon failure to prevent this condition.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel had a use-after-free vulnerability in the reserved memory subsystem. Specifically, if alloc_reserved_mem_array() fails, the global pointer reserved_mem continues to reference reserved_mem_array located in __initdata, which has been freed. Since of_reserved_mem_lookup() is available for use after initialization, it could dereference this freed memory, causing a use-after-free condition. The vulnerability was addressed by resetting reserved_mem_count to 0 when alloc_reserved_mem_array() fails, preventing access to freed memory.
Potential Impact
This vulnerability could lead to use-after-free conditions in the kernel, potentially causing system instability or crashes. No information about exploitation in the wild or privilege escalation is provided.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to reset reserved_mem_count to 0 when alloc_reserved_mem_array() fails, preventing use-after-free. Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; check the Linux kernel vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9fvr-rjg6-fvw4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74352"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a808b6abf8831d5394f635d
Added to database: 08/15/2026, 15:53:14 UTC
Last enriched: 08/15/2026, 16:05:20 UTC
Last updated: 08/15/2026, 16:05:20 UTC
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.