CVE-2026-23067

Source
https://cve.org/CVERecord?id=CVE-2026-23067
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23067.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-23067
Downstream
Published
2026-02-04T16:07:48.457Z
Modified
2026-04-02T13:11:54.303765Z
Summary
iommu/io-pgtable-arm: fix size_t signedness bug in unmap path
Details

In the Linux kernel, the following vulnerability has been resolved:

iommu/io-pgtable-arm: fix size_t signedness bug in unmap path

__armlpaeunmap() returns sizet but was returning -ENOENT (negative error code) when encountering an unmapped PTE. Since sizet is unsigned, -ENOENT (typically -2) becomes a huge positive value (0xFFFFFFFFFFFFFFFE on 64-bit systems).

This corrupted value propagates through the call chain: __armlpaeunmap() returns -ENOENT as sizet -> armlpaeunmappages() returns it -> _iommuunmap() adds it to iova address -> iommupgsize() triggers BUGON due to corrupted iova

This can cause IOVA address overflow in _iommuunmap() loop and trigger BUGON in iommupgsize() from invalid address alignment.

Fix by returning 0 instead of -ENOENT. The WARNON already signals the error condition, and returning 0 (meaning "nothing unmapped") is the correct semantic for sizet return type. This matches the behavior of other io-pgtable implementations (io-pgtable-arm-v7s, io-pgtable-dart) which return 0 on error conditions.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23067.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
3318f7b5cefbff96b1bb49584ac38d2c9997a830
Fixed
41ec6988547819756fb65e94fc24f3e0dddf84ac
Fixed
374e7af67d9d9d6103c2cfc8eb32abfecf3a2fd8

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23067.json"