Skip to content
Fencer Intel
critical 9.8

CVE-2023-38429 in the critical feed json

An issue was discovered in the Linux kernel before 6.3.4.

published 3y ago modified 5mo ago also EUVD-2023-42246

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

An issue was discovered in the Linux kernel before 6.3.4. fs/ksmbd/connection.c in ksmbd has an off-by-one error in memory allocation (because of ksmbd_smb2_check_message) that may lead to out-of-bounds access.

Patch / fix

  • linux linux_kernel 5.15.113, 6.1.30, 6.3.4
  • linux Debian 12 6.1.37-1
  • linux Debian 14, Debian 13 6.3.7-1

debian advisories DEBIAN-CVE-2023-38429

  • linux Ubuntu 22.04 LTS 5.15.0-83.92
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1044.49
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1041.49
  • linux-gke Ubuntu 22.04 LTS 5.15.0-1041.46
  • linux-ibm Ubuntu 22.04 LTS 5.15.0-1037.40
  • linux-kvm Ubuntu 22.04 LTS 5.15.0-1041.46
  • linux-azure Ubuntu 22.04 LTS 5.15.0-1046.53
  • linux-gkeop Ubuntu 22.04 LTS 5.15.0-1027.32

ubuntu advisories UBUNTU-CVE-2023-38429

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 CBL-Mariner 2.0 5.15.122.1-2

azure linux advisories AZL-27535

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

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

Exploit prediction

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

CVSS scores

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

Classification

Weakness
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.