NVD / CVE Program· CNA redhat

CVE-2022-2526: A use-after-free vulnerability was found in systemd.

Noroxi assessment

Priority: Monitor (action score 39/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: 1.3% (FIRST EPSS); higher than 71.1% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: systemd (AlmaLinux:8) 239-58.el8_6.4; systemd-container (AlmaLinux:8) 239-58.el8_6.4; systemd-devel (AlmaLinux:8) 239-58.el8_6.4.

Low priority for now. Upgrade to systemd (AlmaLinux:8) 239-58.el8_6.4; systemd-container (AlmaLinux:8) 239-58.el8_6.4; systemd-devel (AlmaLinux:8) 239-58.el8_6.4 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

A use-after-free vulnerability was found in systemd. This issue occurs due to the on_stream_io() function and dns_stream_complete() function in 'resolved-dns-stream.c' not incrementing the reference counting for the DnsStream object. Therefore, other functions and callbacks called can dereference the DNSStream object, causing the use-after-free when the reference is still used later.

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Published: Sep 9, 2022
Updated: Jun 17, 2026
EPSS: 1.3% · 71th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.3%

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

Is your version affected? Check it

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 help

Affected 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
systemd project	systemd	cpe:2.3:a:systemd_project:systemd
netapp	active iq unified manager	cpe:2.3:a:netapp:active_iq_unified_manager
netapp	h300s firmware	cpe:2.3:o:netapp:h300s_firmware
netapp	h300s	cpe:2.3:h:netapp:h300s
netapp	h500s firmware	cpe:2.3:o:netapp:h500s_firmware
netapp	h500s	cpe:2.3:h:netapp:h500s
netapp	h700s firmware	cpe:2.3:o:netapp:h700s_firmware
netapp	h700s	cpe:2.3:h:netapp:h700s
netapp	h410s firmware	cpe:2.3:o:netapp:h410s_firmware
netapp	h410s	cpe:2.3:h:netapp:h410s

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

netapp active iq unified managerall versions
netapp h300s firmwareall versions
netapp h410s firmwareall versions
netapp h500s firmwareall versions
netapp h700s firmwareall versions
systemd project systemd240

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

n/a systemd-resolved
- systemd 240affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:8	systemd	before 239-58.el8_6.4	239-58.el8_6.4
AlmaLinux:8	systemd-container	before 239-58.el8_6.4	239-58.el8_6.4
AlmaLinux:8	systemd-devel	before 239-58.el8_6.4	239-58.el8_6.4
AlmaLinux:8	systemd-journal-remote	before 239-58.el8_6.4	239-58.el8_6.4
AlmaLinux:8	systemd-libs	before 239-58.el8_6.4	239-58.el8_6.4
AlmaLinux:8	systemd-pam	before 239-58.el8_6.4	239-58.el8_6.4
AlmaLinux:8	systemd-tests	before 239-58.el8_6.4	239-58.el8_6.4
AlmaLinux:8	systemd-udev	before 239-58.el8_6.4	239-58.el8_6.4
Debian:12	systemd	before 240-1	240-1
Red Hat:enterprise_linux:7::client	libgudev1	before 0:219-78.el7_9.7	0:219-78.el7_9.7
Red Hat:enterprise_linux:7::client	libgudev1-devel	before 0:219-78.el7_9.7	0:219-78.el7_9.7
Red Hat:enterprise_linux:7::client	systemd	before 0:219-78.el7_9.7	0:219-78.el7_9.7
Red Hat:enterprise_linux:7::client	systemd-debuginfo	before 0:219-78.el7_9.7	0:219-78.el7_9.7
Red Hat:enterprise_linux:7::client	systemd-devel	before 0:219-78.el7_9.7	0:219-78.el7_9.7
Red Hat:enterprise_linux:7::client	systemd-journal-gateway	before 0:219-78.el7_9.7	0:219-78.el7_9.7
Red Hat:enterprise_linux:7::client	systemd-libs	before 0:219-78.el7_9.7	0:219-78.el7_9.7
Red Hat:enterprise_linux:7::client	systemd-networkd	before 0:219-78.el7_9.7	0:219-78.el7_9.7
Red Hat:enterprise_linux:7::client	systemd-python	before 0:219-78.el7_9.7	0:219-78.el7_9.7
Red Hat:enterprise_linux:7::client	systemd-resolved	before 0:219-78.el7_9.7	0:219-78.el7_9.7
Red Hat:enterprise_linux:7::client	systemd-sysv	before 0:219-78.el7_9.7	0:219-78.el7_9.7
Red Hat:enterprise_linux:8::baseos	systemd	before 0:239-58.el8_6.4	0:239-58.el8_6.4
Red Hat:enterprise_linux:8::baseos	systemd-container	before 0:239-58.el8_6.4	0:239-58.el8_6.4
Red Hat:enterprise_linux:8::baseos	systemd-container-debuginfo	before 0:239-58.el8_6.4	0:239-58.el8_6.4
Red Hat:enterprise_linux:8::baseos	systemd-debuginfo	before 0:239-58.el8_6.4	0:239-58.el8_6.4

+63

Same product

systemd project: all records

Other highest-scoring records for the same primary product.

CVE-2017-9445In systemd through 233, certain sizes passed to dns_packet_new in systemd-resolved can cause it to allocate a buffer that's too small.
46Plan
CVE-2018-21029systemd 239 through 245 accepts any certificate signed by a trusted certificate authority for DNS Over TLS.
40Plan
CVE-2015-7510Stack-based buffer overflow in the getpwnam and getgrnam functions of the NSS module nss-mymachines in systemd.
40Plan

Published before and after this one in the same product

← EarlierCVE-2021-33910Jul 20, 2021 · basic/unit-name.c in systemd prior to 246.15, 247.8, 248.5, and 249.1 has a Memory Allocation with an Excessive Size Value (involving strdup
25Monitor
← EarlierCVE-2021-3997Aug 23, 2022 · A flaw was found in systemd.
23Monitor
Later →CVE-2022-3821Nov 8, 2022 · An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c.
22Monitor

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
almalinux:systemd	239-58.el8_6.4 · AlmaLinux:8	Package registry (OSV)
almalinux:systemd-container	239-58.el8_6.4 · AlmaLinux:8	Package registry (OSV)
almalinux:systemd-devel	239-58.el8_6.4 · AlmaLinux:8	Package registry (OSV)
almalinux:systemd-journal-remote	239-58.el8_6.4 · AlmaLinux:8	Package registry (OSV)
almalinux:systemd-libs	239-58.el8_6.4 · AlmaLinux:8	Package registry (OSV)
almalinux:systemd-pam	239-58.el8_6.4 · AlmaLinux:8	Package registry (OSV)
almalinux:systemd-tests	239-58.el8_6.4 · AlmaLinux:8	Package registry (OSV)
almalinux:systemd-udev	239-58.el8_6.4 · AlmaLinux:8	Package registry (OSV)
debian:systemd	240-1 · Debian:12	Package registry (OSV)
red hat:libgudev1	0:219-78.el7_9.7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:libgudev1-devel	0:219-78.el7_9.7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:systemd	0:219-78.el7_9.7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:systemd-container	0:239-45.el8_4.12 · Red Hat:rhel_eus:8.4::baseos	Package registry (OSV)
red hat:systemd-debuginfo	0:219-78.el7_9.7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:systemd-devel	0:219-78.el7_9.7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:systemd-journal-gateway	0:219-78.el7_9.7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:systemd-libs	0:219-78.el7_9.7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:systemd-networkd	0:219-78.el7_9.7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:systemd-python	0:219-78.el7_9.7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:systemd-resolved	0:219-78.el7_9.7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:systemd-sysv	0:219-78.el7_9.7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
rocky linux:systemd	0:239-58.el8_6.4 · Rocky Linux:8	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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

systemd/systemdcommit d973d94

Credits

All researchers

Finders, 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

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

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✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/systemd/systemd/commit/d973d94dec349fb676fdd844f6fe2ada3538f27c

Show all references (1 more)

security.netapp.com/advisory/ntap-20221111-0005/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records