Skip to content
Fencer Intel
critical 9.1

CVE-2023-52442 in the critical feed json

ksmbd: validate session id and tree id in compound request

published 2y ago modified 3mo ago also EUVD-2023-57067

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
29.6%
EPSS 29.6% 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 session id and tree id in compound request

`smb2_get_msg()` in smb2_get_ksmbd_tcon() and smb2_check_user_session() will always return the first request smb2 header in a compound request. if `SMB2_TREE_CONNECT_HE` is the first command in compound request, will return 0, i.e. The tree id check is skipped. This patch use ksmbd_req_buf_next() to get current command in compound.

Patch / fix

  • Linux Linux 5.15.145, 6.1.53, 6.4.16, 6.5
  • linux Debian 12 6.1.55-1
  • linux Debian 14, Debian 13 6.5.3-1

debian advisories DEBIAN-CVE-2023-52442

  • linux-gkeop-5.15 Ubuntu 20.04 LTS 5.15.0-1040.46~20.04.1

ubuntu advisories UBUNTU-CVE-2023-52442

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

Is CVE-2023-52442 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

29.64% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-20).

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
CISA ADP 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.