Home/CVE/In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: Use variable length array instead of fixe
CVE
CVE-2024-38623
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: Use variable length array instead of fixe
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Use variable length array instead of fixed size Should fix smatch warning: ntfs_set_label() error: __builtin_memcpy() 'uni-name' too small (20 vs 256)
CRITICAL · CVSS 9.8
EPSS 0.00248
Schedule remediation
- SSVC automatable: yes - attacks can be scripted at scale
- CVSS base score ≥ 7.0
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2024-38623, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
1Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
1Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
⬡
Weakness Classification
▤
Affected Products & Versions
4linux kernel>= 5.15 and < 5.15.161
linux kernel>= 5.16 and < 6.1.93
linux kernel>= 6.2 and < 6.6.33
linux kernel>= 6.7 and < 6.9.4
▤
Affected Packages
38Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Ubuntu:14.04:LTS
linux
fixed in 3.11.0-12.19
Ubuntu:14.04:LTS
linux-aws
fixed in 4.4.0-1002.2
Ubuntu:14.04:LTS
linux-azure
fixed in 4.15.0-1023.24~14.04.1
Ubuntu:14.04:LTS
linux-lts-xenial
fixed in 4.4.0-13.29~14.04.1
Ubuntu:16.04:LTS
linux
fixed in 4.4.0-2.16
Ubuntu:16.04:LTS
linux-aws
fixed in 4.4.0-1001.10
Ubuntu:16.04:LTS
linux-aws-hwe
fixed in 4.15.0-1030.31~16.04.1
Ubuntu:16.04:LTS
linux-azure
fixed in 4.11.0-1009.9
Ubuntu:16.04:LTS
linux-gcp
fixed in 4.10.0-1004.4
Ubuntu:16.04:LTS
linux-hwe
fixed in 4.8.0-39.42~16.04.1
Ubuntu:16.04:LTS
linux-kvm
fixed in 4.4.0-1004.9
Ubuntu:16.04:LTS
linux-oracle
fixed in 4.15.0-1007.9~16.04.1
Ubuntu:18.04:LTS
linux
fixed in 4.13.0-16.19
Ubuntu:18.04:LTS
linux-aws
fixed in 4.15.0-1001.1
Ubuntu:18.04:LTS
linux-aws-5.4
fixed in 5.4.0-1018.18~18.04.1
Ubuntu:18.04:LTS
linux-azure-4.15
fixed in 4.15.0-1082.92
Ubuntu:18.04:LTS
linux-azure-5.4
fixed in 5.4.0-1020.20~18.04.1
Ubuntu:18.04:LTS
linux-gcp-4.15
fixed in 4.15.0-1071.81
Ubuntu:18.04:LTS
linux-gcp-5.4
fixed in 5.4.0-1019.19~18.04.2
Ubuntu:18.04:LTS
linux-hwe-5.4
fixed in 5.4.0-37.41~18.04.1
Ubuntu:18.04:LTS
linux-hwe-edge
fixed in 5.0.0-15.16~18.04.1
Ubuntu:18.04:LTS
linux-ibm-5.4
fixed in 5.4.0-1010.11~18.04.2
Ubuntu:18.04:LTS
linux-kvm
fixed in 4.15.0-1002.2
Ubuntu:18.04:LTS
linux-oracle
fixed in 4.15.0-1007.9
Ubuntu:18.04:LTS
linux-oracle-5.4
fixed in 5.4.0-1019.19~18.04.1
Ubuntu:18.04:LTS
linux-raspi-5.4
fixed in 5.4.0-1013.13~18.04.1
Ubuntu:20.04:LTS
linux
fixed in 5.4.0-9.12
Ubuntu:20.04:LTS
linux-aws
fixed in 5.4.0-1005.5
Ubuntu:20.04:LTS
linux-aws-5.11
Ubuntu:20.04:LTS
linux-aws-5.13
Ubuntu:20.04:LTS
linux-aws-5.15
fixed in 5.15.0-1069.75~20.04.1
Ubuntu:20.04:LTS
linux-aws-5.8
Ubuntu:20.04:LTS
linux-azure
fixed in 5.4.0-1006.6
Ubuntu:20.04:LTS
linux-azure-5.11
Ubuntu:20.04:LTS
linux-azure-5.13
Ubuntu:20.04:LTS
linux-azure-5.15
fixed in 5.15.0-1072.81~20.04.1
Ubuntu:20.04:LTS
linux-azure-5.8
Ubuntu:20.04:LTS
linux-azure-fde
📦
Fixed versions by distribution
19The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
suse sle15cluster-md-kmp-default open
suse sle15dlm-kmp-default open
suse sle15gfs2-kmp-default open
suse sle15kernel-default open
suse sle15kernel-default-base open
suse sle15kernel-default-devel open
suse sle15kernel-default-extra open
suse sle15kernel-default-livepatch open
suse sle15kernel-default-livepatch-devel open
suse sle15kernel-default-man open
suse sle15kernel-devel open
suse sle15kernel-devel-azure open
suse sle15kernel-devel-rt open
suse sle15kernel-macros open
suse sle15kernel-source open
suse sle15kernel-source-azure open
suse sle15kernel-source-rt open
suse sle15ocfs2-kmp-default open
suse sle15reiserfs-kmp-default open
▣
Scoring & Timeline
9.8
CRITICAL · CVSS v3.1 · 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Technical impact
total
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
⚑
Vendor Advisories
13🔗
References & Sources
5Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.