Skip to content
Fencer Vulns
critical 9.1

CVE-2023-38430 in the critical feed json

An issue was discovered in the Linux kernel before 6.3.9.

published 2023-07-17 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-42247

cvss
9.1
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 67%
public exploits
0
none known

Summary

An issue was discovered in the Linux kernel before 6.3.9. ksmbd does not validate the SMB request protocol ID, leading to an out-of-bounds read.

Patch / fix

  • linux linux_kernel 5.15.145, 6.1.35, 6.3.9
  • linux Debian 12 6.1.37-1
  • linux Debian 14, Debian 13 6.3.11-1

debian advisories DEBIAN-CVE-2023-38430

  • linux Ubuntu 22.04 LTS 5.15.0-102.112
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1057.63
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1055.63
  • linux-gke Ubuntu 22.04 LTS 5.15.0-1054.59
  • linux-ibm Ubuntu 22.04 LTS 5.15.0-1050.53
  • linux-kvm Ubuntu 22.04 LTS 5.15.0-1054.59
  • linux-azure Ubuntu 22.04 LTS 5.15.0-1060.69
  • linux-gkeop Ubuntu 22.04 LTS 5.15.0-1040.46

ubuntu advisories UBUNTU-CVE-2023-38430

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-27534

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

Exploit prediction

1.17% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns 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.