In the Linux kernel, the following vulnerability has been resolved: misc: fastrpc: take fl->lock when moving mmaps on interrupted invoke When an… (CVE-2026-74646)
A vulnerability in the Linux kernel's fastrpc component was resolved by ensuring proper locking when moving memory maps (mmaps) during an interrupted invoke operation. The issue involved missing the fl->lock lock around list operations on mmap buffers when an invoke was interrupted by a signal, potentially causing concurrency issues.
AI Analysis
Technical Summary
The Linux kernel's fastrpc driver had a concurrency vulnerability where, if an invoke operation was interrupted by a signal, the function fastrpc_internal_invoke() moved buffers from fl->mmaps to cctx->invoke_interrupted_mmaps without holding the fl->lock. This lock is normally used to serialize access to fl->mmaps in other functions like fastrpc_req_mmap() and fastrpc_req_munmap(). The absence of this lock during the move operation could lead to race conditions or data corruption. The fix involved taking the fl->lock around the move operation to match the locking discipline used elsewhere.
Potential Impact
The vulnerability could lead to race conditions or inconsistent state in the fastrpc memory map management when an invoke is interrupted by a signal. This may cause instability or unexpected behavior in the kernel's fastrpc subsystem. No direct exploitation or impact details are provided.
Mitigation Recommendations
A fix has been applied to the Linux kernel to take the fl->lock when moving mmaps on interrupted invoke operations. Users should update to a kernel version that includes this fix. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the exact fixed versions and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: misc: fastrpc: take fl->lock when moving mmaps on interrupted invoke When an… (CVE-2026-74646)
Description
A vulnerability in the Linux kernel's fastrpc component was resolved by ensuring proper locking when moving memory maps (mmaps) during an interrupted invoke operation. The issue involved missing the fl->lock lock around list operations on mmap buffers when an invoke was interrupted by a signal, potentially causing concurrency issues.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's fastrpc driver had a concurrency vulnerability where, if an invoke operation was interrupted by a signal, the function fastrpc_internal_invoke() moved buffers from fl->mmaps to cctx->invoke_interrupted_mmaps without holding the fl->lock. This lock is normally used to serialize access to fl->mmaps in other functions like fastrpc_req_mmap() and fastrpc_req_munmap(). The absence of this lock during the move operation could lead to race conditions or data corruption. The fix involved taking the fl->lock around the move operation to match the locking discipline used elsewhere.
Potential Impact
The vulnerability could lead to race conditions or inconsistent state in the fastrpc memory map management when an invoke is interrupted by a signal. This may cause instability or unexpected behavior in the kernel's fastrpc subsystem. No direct exploitation or impact details are provided.
Mitigation Recommendations
A fix has been applied to the Linux kernel to take the fl->lock when moving mmaps on interrupted invoke operations. Users should update to a kernel version that includes this fix. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the exact fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-487q-3fxv-jwrm
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74646"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f2acd9273b499bc852
Added to database: 08/22/2026, 22:51:30 UTC
Last enriched: 08/22/2026, 23:27:03 UTC
Last updated: 08/23/2026, 00:12:05 UTC
Views: 2
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.