Dismissed
(max. allowed matches exceeded)
Permalink
CVE-2026-63926
8.4 HIGH
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Local (L)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): None (N)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): High (H)
- Integrity (I): High (H)
- Availability (A): High (H)
- Modified Attack Vector (MAV): Local (L)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): None (N)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): High (H)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): High (H)
- Modified Availability (MA): High (H)
Activity log
- Created & dismissed (max. allowed matches exceeded) suggestion
bpf: sockmap: fix tail fragment offset in bpf_msg_push_data
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.
References
Affected products
Linux
- <63f64a510c7917658ddf4d073ece73914ee25346
- <f72eed9b84fb771019a955908132410a9ba9ea3f
- <f14609d8146707452e0822f3c8154674ce677251
- <96b72672ce849a1402730238e64d9b20bf06a96d
- =<6.18.*
- ==4.20
- <d81b323af2dcee47573907ccb89c0df9b45cb2e2
- =<7.0.*
- =<6.12.*
- <3075c21d2d76c0067f4a382765b43d6cc10470f1
- <aeb95146848d12206e1b2cfacd4f40e21ce81d94
- =<6.1.*
- =<*
- =<6.6.*
- <4.20
- <5e19028667963fb371ebb00cecc2a473ef92056b
- =<5.15.*
- =<5.10.*