SECUFOCUSNOW
Home›CVE index›CVE-2026-63926
Review reviewHigh

CVE-2026-63926

Linux

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`, whic...

CVSS
8.4
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.20
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 8.4

Vulnerability overview

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`, whic...

Affected product and versions

Product
Linux
Affected versions
>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 < f14609d8146707452e0822f3c8154674ce677251, >= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 < d81b323af2dcee47573907ccb89c0df9b45cb2e2, >= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 < aeb95146848d12206e1b2cfacd4f40e21ce81d94, >= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 < 96b72672ce849a1402730238e64d9b20bf06a96d, >= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 < 3075c21d2d76c0067f4a382765b43d6cc10470f1, >= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 < 5e19028667963fb371ebb00cecc2a473ef92056b, >= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 < 63f64a510c7917658ddf4d073ece73914ee25346, >= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 < f72eed9b84fb771019a955908132410a9ba9ea3f, >= 4.20
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
Not available