arm64: io: Extract user memory type in ioremap_prot()
In the Linux kernel, the following vulnerability has been resolved: arm64: io: Extract user memory type in ioremap_prot() The only caller of ioremap_prot() outside of the generic ioremap() implementation is generic_access_phys(), which passes a 'pgprot_t' value determined from the user mapping of the target 'pfn' being accessed by the kernel. On arm64, the 'pgprot_t' contains all of the non-address bits from the pte, including the permission controls, and so we end up returning a new user mapping from ioremap_prot() which faults when accessed from the kernel on systems with PAN: | Unable to handle kernel read from unreadable memory at virtual address ffff80008ea89000 | ... | Call trace: | __memcpy_fromio+0x80/0xf8 | generic_access_phys+0x20c/0x2b8 | __access_remote_vm+0x46c/0x5b8 | access_remote_vm+0x18/0x30 | environ_read+0x238/0x3e8 | vfs_read+0xe4/0x2b0 | ksys_read+0xcc/0x178 | __arm64_sys_read+0x4c/0x68 Extract only the memory type from the user 'pgprot_t' in ioremap_prot() and assert that we're being passed a user mapping, to protect us against any changes in future that may require additional handling. To avoid falsely flagging users of ioremap(), provide our own ioremap() macro which simply wraps __ioremap_prot().
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.93, 6.18.17, 6.19.7, 6.6.143
- CVEs
- CVE-2026-23346
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 16:36 UTC · Revision 1
Source evidence
arm64: io: Extract user memory type in ioremap_prot()
core-osv · Original sourcePublished 25 Mar 2026, 10:27 UTC
In the Linux kernel, the following vulnerability has been resolved: arm64: io: Extract user memory type in ioremap_prot() The only caller of ioremap_prot() outside of the generic ioremap() implementation is generic_access_phys(), which passes a 'pgprot_t' value determined from the user mapping of the target 'pfn' being accessed by the kernel. On arm64, the 'pgprot_t' contains all of the non-address bits from the pte, including the permission controls, and so we end up returning a new user mapping from ioremap_prot() which faults when accessed from the kernel on systems with PAN: | Unable to handle kernel read from unreadable memory at virtual address ffff80008ea89000 | ... | Call trace: | __memcpy_fromio+0x80/0xf8 | generic_access_phys+0x20c/0x2b8 | __access_remote_vm+0x46c/0x5b8 | access_remote_vm+0x18/0x30 | environ_read+0x238/0x3e8 | vfs_read+0xe4/0x2b0 | ksys_read+0xcc/0x178 | __arm64_sys_read+0x4c/0x68 Extract only the memory type from the user 'pgprot_t' in ioremap_prot() and assert that we're being passed a user mapping, to protect us against any changes in future that may require additional handling. To avoid falsely flagging users of ioremap(), provide our own ioremap() macro which simply wraps __ioremap_prot().
osv:CVE-2026-23346
Kernel
Fixed versions: 6.6.143, 6.12.93, 6.18.17, 6.19.7
Complete source record
{
"id": "6c9494be9a8e2ac5ed659d0bb641a3a9f14cd937ffdb963f810cd6009a97ed93",
"url": "https://osv.dev/vulnerability/CVE-2026-23346",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "arm64: io: Extract user memory type in ioremap_prot()",
"summary": "In the Linux kernel, the following vulnerability has been resolved: arm64: io: Extract user memory type in ioremap_prot() The only caller of ioremap_prot() outside of the generic ioremap() implementation is generic_access_phys(), which passes a 'pgprot_t' value determined from the user mapping of the target 'pfn' being accessed by the kernel. On arm64, the 'pgprot_t' contains all of the non-address bits from the pte, including the permission controls, and so we end up returning a new user mapping from ioremap_prot() which faults when accessed from the kernel on systems with PAN: | Unable to handle kernel read from unreadable memory at virtual address ffff80008ea89000 | ... | Call trace: | __memcpy_fromio+0x80/0xf8 | generic_access_phys+0x20c/0x2b8 | __access_remote_vm+0x46c/0x5b8 | access_remote_vm+0x18/0x30 | environ_read+0x238/0x3e8 | vfs_read+0xe4/0x2b0 | ksys_read+0xcc/0x178 | __arm64_sys_read+0x4c/0x68 Extract only the memory type from the user 'pgprot_t' in ioremap_prot() and assert that we're being passed a user mapping, to protect us against any changes in future that may require additional handling. To avoid falsely flagging users of ioremap(), provide our own ioremap() macro which simply wraps __ioremap_prot().",
"evidence": "osv:CVE-2026-23346",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.6.143",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.93",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.17",
"evidence": "/affected/1/ranges"
},
{
"value": "6.19.7",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-23346",
"aliases": [
"CVE-2026-23346"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "893dea9ccd08dab924839354aba21d4ed7a9abc0"
},
{
"fixed": "64858b76ec67c5fc40fef8ec1841fecb78c1ebde"
},
{
"fixed": "eeecafce5afffb4da703666ebefbd4d6e2a5abf6"
},
{
"fixed": "3d64dcc0799c2d6921ba027716b7be721eb19fa8"
},
{
"fixed": "d1ad8fe7f72d73e1617bac79f2ec7a3bedf47e2a"
},
{
"fixed": "8f098037139b294050053123ab2bc0f819d08932"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23346.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.6.143"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.93"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.17"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "6.19.7"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23346.json"
}
}
],
"modified": "2026-10-28T02:30:30.810152230Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/3d64dcc0799c2d6921ba027716b7be721eb19fa8",
"https://git.kernel.org/stable/c/64858b76ec67c5fc40fef8ec1841fecb78c1ebde",
"https://git.kernel.org/stable/c/8f098037139b294050053123ab2bc0f819d08932",
"https://git.kernel.org/stable/c/d1ad8fe7f72d73e1617bac79f2ec7a3bedf47e2a",
"https://git.kernel.org/stable/c/eeecafce5afffb4da703666ebefbd4d6e2a5abf6",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23346.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-23346",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23346.json"
}
},
"related_cves": [
{
"value": "CVE-2026-23346",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 497457,
"published_at": "2026-03-25T10:27:33.133+00:00"
}