iommu/s390: Fix NULL dereference in iova_to_phys() with ZPCI_TABLE_TYPE_RFX
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.53, 7.2.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: iommu/s390: Fix NULL dereference in iova_to_phys() with ZPCI_TABLE_TYPE_RFX When using a 5-level translation table via ZPCI_TABLE_TYPE_RFX get_rso_from_iova() returns NULL when the region-first entry is invalid. Yet in get_rto_from_iova() the region-second origin rso is not checked to be non-NULL before accessing rso[rsx] leading to a NULL pointer dereference instead of a NULL return when iova_to_phys() is called on a unmapped IOVA. Fix this by adding the missing NULL check.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 81244074b518aeb90de5f68e7e825564c29c5c50 · fixed in d0502ed0a1aae97e2ab7a21545903ba612d9f02e; From 81244074b518aeb90de5f68e7e825564c29c5c50 · fixed in 41b5e0ce6801bf04d8fd3bca46e8c393349ebd5c; From 81244074b518aeb90de5f68e7e825564c29c5c50 · fixed in 20db6573301e66cd65ebf6c130b6563c69374d9d
- Linux Linux
6.16
- KernelLinux
From 6.16.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.7