PatchSiren cyber security CVE debrief
CVE-2026-97585 Linux CVE debrief
A double-unmap vulnerability in the Linux kernel's afs_edit_dir_remove() function has been resolved. The vulnerability occurs when manually kunmapping blocks without clearing iter.blocks, which can result in a double-kunmap if afs_dir_find_block() is called twice in a row. This issue can have significant impacts on the stability and security of affected Linux kernel deployments. Linux kernel developers and maintainers should review the patch notes and verify the afs_edit_dir_remove() function implementation to ensure the vulnerability is properly addressed.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-25
- Original CVE updated
- 2026-09-25
- Advisory published
- 2026-09-25
- Advisory updated
- 2026-09-25
Who should care
Linux kernel developers and maintainers, Linux distribution maintainers, and security teams responsible for managing Linux kernel deployments. These stakeholders should review the patch notes, verify the afs_edit_dir_remove() function implementation, and monitor for potential issues with the afs_dir_find_block() function to ensure the vulnerability is properly addressed.
Why it matters
The CVE-2026-97585 vulnerability in the Linux kernel's afs_edit_dir_remove() function requires verification of patch implementation to prevent double-unmap issues. Linux kernel developers and maintainers should review the patch notes and verify the afs_edit_dir_remove() function implementation.
- Verify Linux kernel patch implementation to prevent double-unmap issues
- Monitor for potential issues with afs_dir_find_block() function
Technical summary
The Linux kernel's afs_edit_dir_remove() function has a double-unmap vulnerability. The function fails to use a cleanup function to unmap the block pointed to by afs_dir_iter::block, leading to potential double-kunmap issues. This vulnerability can be triggered when afs_dir_find_block() is called twice in a row, resulting in a double-kunmap of the same block. To address this issue, Linux kernel developers and maintainers should review the patch notes and verify the afs_edit_dir_remove() function implementation to ensure the vulnerability is properly addressed.
Defensive priority
Low
Recommended defensive actions
- Review Linux kernel patch notes for CVE-2026-97585
- Verify afs_edit_dir_remove() function implementation
- Monitor for potential double-unmap issues in Linux kernel
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record and NVD entry provide limited information about the vulnerability. The Linux kernel patch notes and Git commit history are available for further analysis. To verify the patch implementation, defenders should review the official advisory, check for affected product deployments, and monitor for potential issues with the afs_dir_find_block() function. Additional analysis of the Linux kernel source code and patch implementation may be necessary to ensure the vulnerability is fully addressed.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-97585 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-97585
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-97585 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-97585
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/9d6c703e24da3d39067e3c75f4ac2f6001c2472f
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/b60f51e4ad0f6f940899788ccc2762db1e3b69e6
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/e3cfd3eb7d5be7787cc69530b423f788f14d084f
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.