CVE-2024-26594 in the critical feed json
ksmbd: validate mech token in session setup
published 2y ago modified 3mo ago also EUVD-2024-23856
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 51.2%
- EPSS 51.2% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: validate mech token in session setup
If client send invalid mech token in session setup request, ksmbd validate and make the error if it is invalid.
Patch / fix
- Linux Linux 5.15.149, 6.1.75, 6.6.14, 6.7.2, 6.8
- linux Debian 12 6.1.76-1
- linux Debian 14, Debian 13 6.6.15-1
debian advisories DEBIAN-CVE-2024-26594
- linux Ubuntu 22.04 LTS 5.15.0-106.116
- linux-aws Ubuntu 22.04 LTS 5.15.0-1061.67
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1059.67
- linux-gke Ubuntu 22.04 LTS 5.15.0-1058.63
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1054.57
- linux-kvm Ubuntu 22.04 LTS 5.15.0-1058.63
- linux-azure Ubuntu 22.04 LTS 5.15.0-1063.72
- linux-gkeop Ubuntu 22.04 LTS 5.15.0-1044.51
ubuntu advisories UBUNTU-CVE-2024-26594
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
- hyperv-daemons CBL-Mariner 2.0 5.15.153.1-1
azure linux advisories AZL-35452
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/dd1de9268745f0eac83a430db7afc32cbd62e84b commit
- git.kernel.org/stable/c/6eb8015492bcc84e40646390e50a862b2c0529c9 commit
- git.kernel.org/stable/c/a2b21ef1ea4cf632d19b3a7cc4d4245b8e63202a commit
- git.kernel.org/stable/c/5e6dfec95833edc54c48605a98365a7325e5541e commit
- git.kernel.org/stable/c/92e470163d96df8db6c4fa0f484e4a229edb903d commit
Is CVE-2024-26594 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-26594 updated cvss 5.5
kernel: ksmbd: validate mech token in session setup
-
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 Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot 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
- partial
- Assessed
- 2y ago
Exploit prediction
51.25% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
| NVD | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
- Technology feeds
References
-
git.kernel.org
/stable/c/dd1de9268745f0eac83a430db7afc32cbd62e84b
patch
-
git.kernel.org
/stable/c/6eb8015492bcc84e40646390e50a862b2c0529c9
patch
-
git.kernel.org
/stable/c/a2b21ef1ea4cf632d19b3a7cc4d4245b8e63202a
patch
-
git.kernel.org
/stable/c/5e6dfec95833edc54c48605a98365a7325e5541e
patch
-
git.kernel.org
/stable/c/92e470163d96df8db6c4fa0f484e4a229edb903d
patch
Sources
- CVE List CVE-2024-26594
- NVD CVE-2024-26594
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.