Kernel-address disclosure via incorrect PK_KMEM assignment
Published Sep 11, 2026 · Updated Sep 18, 2026
Information disclosure in NetBSD 9.0 through 9.4 and 10.0 through 10.1 allows local users to read kernel virtual addresses. The mm_open() path in sys/dev/mm.c assigns PK_KMEM to processes that open world-accessible /dev/null or /dev/zero, so KERN_PROC sysctl queries bypass CANSEE_KPTR pointer obfuscation. Any unprivileged local account can expose addresses for kernel structures, but the published impact does not include data modification or service interruption.
Summary
What happened
Information disclosure in NetBSD 9.0 through 9.4 and 10.0 through 10.1 allows local users to read kernel virtual addresses. The mm_open() path in sys/dev/mm.c assigns PK_KMEM to processes that open world-accessible /dev/null or /dev/zero, so KERN_PROC sysctl queries bypass CANSEE_KPTR pointer obfuscation. Any unprivileged local account can expose addresses for kernel structures, but the published impact does not include data modification or service interruption.
The record
- CVE
- CVE-2026-57843
- Published
- Sep 11, 2026
- Updated
- Sep 18, 2026
- Vendor
- The NetBSD Foundation
- Product
- NetBSD
- Classifications
- CWE-732
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 11, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0 <=10.1
- Affected versionversion=9.0 <9.5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started