bpf: sockmap: fix tail fragment offset in bpf_msg_push_data
- 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.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, 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: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: sockmap: fix tail fragment offset in bpf_msg_push_data When bpf_msg_push_data() inserts data in the middle of a scatterlist entry, it splits the original entry into a left fragment and a right fragment. The right fragment offset is page-local, but the code advances it with `start`, which is the message-global insertion point. For inserts into a non-first SG entry, this over-advances the offset and leaves the split layout inconsistent. Advance the right fragment offset by the fragment-local delta, `start - offset`, which matches the length removed from the front of the original entry.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 · fixed in f14609d8146707452e0822f3c8154674ce677251; From 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 · fixed in d81b323af2dcee47573907ccb89c0df9b45cb2e2; From 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 · fixed in aeb95146848d12206e1b2cfacd4f40e21ce81d94; From 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 · fixed in 96b72672ce849a1402730238e64d9b20bf06a96d; From 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 · fixed in 3075c21d2d76c0067f4a382765b43d6cc10470f1; From 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 · fixed in 5e19028667963fb371ebb00cecc2a473ef92056b; From 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 · fixed in 63f64a510c7917658ddf4d073ece73914ee25346; From 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 · fixed in f72eed9b84fb771019a955908132410a9ba9ea3f
- Linux Linux
4.20
- KernelLinux
From 4.20.0 · fixed in 5.10.259; From 5.11.0 · fixed in 5.15.210; From 5.16.0 · fixed in 6.1.176; From 6.2.0 · fixed in 6.6.143; From 6.7.0 · fixed in 6.12.93; From 6.13.0 · fixed in 6.18.35; From 6.19.0 · fixed in 7.0.12
References 8
git.kernel.org
- stable/c/f14609d8146707452e0822f3c8154674ce677251
- stable/c/d81b323af2dcee47573907ccb89c0df9b45cb2e2
- stable/c/aeb95146848d12206e1b2cfacd4f40e21ce81d94
- stable/c/96b72672ce849a1402730238e64d9b20bf06a96d
- stable/c/3075c21d2d76c0067f4a382765b43d6cc10470f1
- stable/c/5e19028667963fb371ebb00cecc2a473ef92056b
- stable/c/63f64a510c7917658ddf4d073ece73914ee25346
- stable/c/f72eed9b84fb771019a955908132410a9ba9ea3f