RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz()
- 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 5.5, 5.9, 5.10, 5.15.222, 6.1.189, and 3 more
- 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: RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() Several corner cases, especially important on 32 bits: • umem->iova is u64, the function argument should pass in u64 or iova will be truncated • Check that the length is not too large for the iova • Check that lengths > 4G don't overflow the GENMASK
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From a40c20dabdf9045270767c75918feb67f0727c89 · fixed in 3014da7587ce006cd08004fd6b257626b314e0a3; From a40c20dabdf9045270767c75918feb67f0727c89 · fixed in ddccf6cc3861de2fe60986933bead79220e0d797; From a40c20dabdf9045270767c75918feb67f0727c89 · fixed in e9bbb5f5349ef560ff6f0395564f04c3aa664559; From a40c20dabdf9045270767c75918feb67f0727c89 · fixed in ae3cf7d2c4d506c5c91746321644e1a08d989e2a; From a40c20dabdf9045270767c75918feb67f0727c89 · fixed in 5fc5b73109540809b094710fac44da81dd8a3ff8; From a40c20dabdf9045270767c75918feb67f0727c89 · fixed in 09ea6837a0434fb4db99528a5055b6d822135dcf; From 5.4.73 · fixed in 5.5; From 5.8.17 · fixed in 5.9; From 5.9.2 · fixed in 5.10
- Linux Linux
5.10
- KernelLinux
From 5.10.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53