Skip to content
Fencer Intel
high 8.8

CVE-2025-40253 json

s390/ctcm: Fix double-kfree

published 11mo ago modified 21d ago also EUVD-2025-201204

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits
0
none known

Summary

In the Linux kernel, the following vulnerability has been resolved:

s390/ctcm: Fix double-kfree

The function 'mpc_rcvd_sweep_req(mpcginfo)' is called conditionally from function 'ctcmpc_unpack_skb'. It frees passed mpcginfo. After that a call to function 'kfree' in function 'ctcmpc_unpack_skb' frees it again.

Remove 'kfree' call in function 'mpc_rcvd_sweep_req(mpcginfo)'.

Bug detected by the clang static analyzer.

Patch / fix

  • Linux Linux 4.10, 4.15, 4.20, 5.4.302, 5.10.247, 5.15.197, 5.18, 6.1.159, 6.6.118, 6.12.60, 6.17.10, 6.18
  • linux Debian 12 6.1.159-1
  • linux Debian 13 6.12.63-1
  • linux Debian 14 6.17.10-1

debian advisories DEBIAN-CVE-2025-40253

  • linux Ubuntu 22.04 LTS 5.15.0-173.183
  • linux Ubuntu 24.04 LTS 6.8.0-106.106
  • linux Ubuntu 25.10 6.17.0-19.19
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1103.110
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1050.53
  • linux-aws Ubuntu 25.10 6.17.0-1009.9
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1103.112
  • linux-gcp Ubuntu 24.04 LTS 6.8.0-1052.55

ubuntu advisories UBUNTU-CVE-2025-40253

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-rt Linux Micro 6.2 6.12.0-160000.28.1
  • kernel-64kb Linux Micro 6.2 6.12.0-160000.28.1
  • kernel-source Linux Micro 6.2 6.12.0-160000.28.1
  • kernel-default Linux Micro 6.2 6.12.0-160000.28.1
  • kernel-default-base Linux Micro 6.2 6.12.0-160000.27.1.160000.2.8
  • gdk-pixbuf Linux Micro 6.2 2.42.12-160000.4.1
  • kernel-syms Linux Micro Extras 6.2 6.12.0-160000.28.1
  • kernel-obs-build Linux Micro Extras 6.2 6.12.0-160000.28.1

suse advisories SUSE-SU-2026:2450-1SUSE-SU-2026:21237-1SUSE-SU-2026:21230-1SUSE-SU-2026:21255-1SUSE-SU-2026:21123-1SUSE-SU-2026:21114-1

  • kernel-rt openSUSE Leap 16.0 6.12.0-160000.28.1
  • dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-64kb openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-syms openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-azure openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-source openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-default openSUSE Leap 16.0 6.12.0-160000.28.1

opensuse advisories openSUSE-SU-2026:20572-1

Is CVE-2025-40253 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-40253 updated cvss 5.5

kernel: s390/ctcm: Fix double-kfree

  • Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
25d ago

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.