RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv
- 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.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.86, and 2 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
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv rxe_rcv() currently checks only that the incoming packet is at least header_size(pkt) bytes long before payload_size() is used. However, payload_size() subtracts both the attacker-controlled BTH pad field and RXE_ICRC_SIZE from pkt->paylen: payload_size = pkt->paylen - offset[RXE_PAYLOAD] - bth_pad(pkt) • RXE_ICRC_SIZE This means a short packet can still make payload_size() underflow even if it includes enough bytes for the fixed headers. Simply requiring header_size(pkt) + RXE_ICRC_SIZE is not sufficient either, because a packet with a forged non-zero BTH pad can still leave payload_size() negative and pass an underflowed value to later receive-path users. Fix this by validating pkt->paylen against the full minimum length required by payload_size(): header_size(pkt) + bth_pad(pkt) + RXE_ICRC_SIZE.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in c4376c672c3648d5bdc31dfffc329d07164f93c4; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 5fedefec757192dcaad29a664ac332c7601be144; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 2c0d71ef12f46c57d37bc571f3f2797db7eb50cc; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 2fd4f8b749309a61c3f3f88ee8891d94f79e1240; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in f83519a4c122c9c7a850a2197648a9ff4c67c520; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 9b924f3a26b21330a837cfe72e819b6393bbeeaa; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in e8ee0e792d475b1067c199ef0af1b6221fa6f43d; From 8700e3e7c4857d28ebaa824509934556da0b3e76 · fixed in 7244491dab347f648e661da96dc0febadd9daec3
- Linux Linux
4.8
- KernelLinux
From 4.8.0 · fixed in 5.10.258; From 5.11.0 · fixed in 5.15.209; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.140; From 6.7.0 · fixed in 6.12.86; From 6.13.0 · fixed in 6.18.27; From 6.19.0 · fixed in 7.0.4
References 8
git.kernel.org
- stable/c/c4376c672c3648d5bdc31dfffc329d07164f93c4
- stable/c/5fedefec757192dcaad29a664ac332c7601be144
- stable/c/2c0d71ef12f46c57d37bc571f3f2797db7eb50cc
- stable/c/2fd4f8b749309a61c3f3f88ee8891d94f79e1240
- stable/c/f83519a4c122c9c7a850a2197648a9ff4c67c520
- stable/c/9b924f3a26b21330a837cfe72e819b6393bbeeaa
- stable/c/e8ee0e792d475b1067c199ef0af1b6221fa6f43d
- stable/c/7244491dab347f648e661da96dc0febadd9daec3