tracing/histogram: Fix a potential memory leak for kstrdup()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 5.4.176, 5.6, 8a8878ebb596281f50fc0b9a6e1f23f0d7f154e8.
Low priority for now. Upgrade to Linux Linux 5.4.176, 5.6, 8a8878ebb596281f50fc0b9a6e1f23f0d7f154e8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: tracing/histogram: Fix a potential memory leak for kstrdup() kfree() is missing on an error path to free the memory allocated by kstrdup(): p = param = kstrdup(data->params[i], GFP_KERNEL); So it is better to free it via kfree(p).
- Published
- Jun 20, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-401
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.4.19 and later · before 5.4.176
- linux linux kernel5.6 and later · before 5.10.96
- linux linux kernel5.11 and later · before 5.15.19
- linux linux kernel5.16 and later · before 5.16.5
- linux linux kernel5.17
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- c78a2baf5e1fe1b38121d6b54bab77ccb81a1a86, 5.6affected
- 38b67e60b6b582e81f9db1b2e7176cbbfbd3e574 and later · before 8a8878ebb596281f50fc0b9a6e1f23f0d7f154e8affected · git
- d380dcde9a07ca5de4805dee11f58a98ec0ad6ff and later · before d71b06aa995007eafd247626d0669b9364c42ad7affected · git
- d380dcde9a07ca5de4805dee11f58a98ec0ad6ff and later · before e33fa4a46ee22de88a700e2e3d033da8214a5175affected · git
- d380dcde9a07ca5de4805dee11f58a98ec0ad6ff and later · before df86e2fe808c3536a9dba353cc2bebdfea00d0cfaffected · git
- d380dcde9a07ca5de4805dee11f58a98ec0ad6ff and later · before e629e7b525a179e29d53463d992bdee759c950fbaffected · git
- 5.4.19 and later · before 5.4.176affected · semver
- 5.5.6 and later · before 5.6affected · semver
- before 5.6not affected · semver
- 5.4.176 and later · up to and including 5.4.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.16.7-1 | 5.16.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2022-48766Jun 20, 2024 · drm/amd/display: Wrap dcn301_calculate_wm_and_dlg for FPU.22Monitor
- ← EarlierCVE-2022-48767Jun 20, 2024 · ceph: properly put ceph_string reference after async create attempt22Monitor
- Later →CVE-2022-48769Jun 20, 2024 · efi: runtime: avoid EFIv2 runtime services on Apple x86 machines22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 5.4.176 | Vendor (CNA) |
| Linux Linux | 5.6 | Vendor (CNA) |
| Linux Linux | 8a8878ebb596281f50fc0b9a6e1f23f0d7f154e8 | Vendor (CNA) |
| Linux Linux | d71b06aa995007eafd247626d0669b9364c42ad7 | Vendor (CNA) |
| Linux Linux | df86e2fe808c3536a9dba353cc2bebdfea00d0cf | Vendor (CNA) |
| Linux Linux | e33fa4a46ee22de88a700e2e3d033da8214a5175 | Vendor (CNA) |
| Linux Linux | e629e7b525a179e29d53463d992bdee759c950fb | Vendor (CNA) |
| debian:linux | 5.16.7-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.