Review reviewHigh

CVE-2026-53110

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: s390/bpf: Zero-extend bpf prog return values and kfunc arguments s390x ABI requires callers to zero-extend unsigned arguments and sign-extend signed arguments, and callees to zero-extend unsigned return values and sign-extend signed return values. s390 BPF JIT currently implements only sign extension. Fix this omission and implement zero extension too.

CVSS
7.8
EPSS
0.12%
2.14% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.12%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: s390/bpf: Zero-extend bpf prog return values and kfunc arguments s390x ABI requires callers to zero-extend unsigned arguments and sign-extend signed arguments, and callees to zero-extend unsigned return values and sign-extend signed return values. s390 BPF JIT currently implements only sign extension. Fix this omission and implement zero extension too.

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 528eb2cb87bc1353235a6384696b4849bde8b0ba < edc90a12073b9a530064a99945c183dde120cb99, >= 528eb2cb87bc1353235a6384696b4849bde8b0ba < 44c4f999b03f55debb1a0c5ab5c1796895a1adf8, >= 528eb2cb87bc1353235a6384696b4849bde8b0ba < 366b0e05ee24f5ba62bdc7ec1346038258b9a797, >= 528eb2cb87bc1353235a6384696b4849bde8b0ba < 834918a77be51419383bf1dda9f02b81ecf26b34, >= 528eb2cb87bc1353235a6384696b4849bde8b0ba < 202e42e4aa890172366354b233c42c73107a3f59, >= 6.3, >= 6.3 < 6.6.141, >= 6.7 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10
Fixed versions
6.6.141, 6.12.91, 6.18.33, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel 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:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available