Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49696: tipc: fix use-after-free Read in tipc_named_reinit

Noroxi assessment

Priority: Monitor (action score 31/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.28% (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 361c5521c1e49843b710f455cae3c0a50b714323, 5.10, 5.5.

Low priority for now. Upgrade to Linux Linux 361c5521c1e49843b710f455cae3c0a50b714323, 5.10, 5.5 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: tipc: fix use-after-free Read in tipc_named_reinit syzbot found the following issue on: ================================================================== BUG: KASAN: use-after-free in tipc_named_reinit+0x94f/0x9b0 net/tipc/name_distr.c:413 Read of size 8 at addr ffff88805299a000 by task kworker/1:9/23764 CPU: 1 PID: 23764 Comm: kworker/1:9 Not tainted 5.18.0-rc4-syzkaller-00878-g17d49e6e8012 #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: events tipc_net_finalize_work Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description.constprop.0.cold+0xeb/0x495 mm/kasan/report.c:313 print_report mm/kasan/report.c:429 [inline] kasan_report.cold+0xf4/0x1c6 mm/kasan/report.c:491 tipc_named_reinit+0x94f/0x9b0 net/tipc/name_distr.c:413 tipc_net_finalize+0x234/0x3d0 net/tipc/net.c:138 process_one_work+0x996/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e9/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298 </TASK> [...] ================================================================== In the commit d966ddcc3821 ("tipc: fix a deadlock when flushing scheduled work"), the cancel_work_sync() function just to make sure ONLY the work tipc_net_finalize_work() is executing/pending on any CPU completed before tipc namespace is destroyed through tipc_exit_net(). But this function is not guaranteed the work is the last queued. So, the destroyed instance may be accessed in the work which will try to enqueue later. In order to completely fix, we re-order the calling of cancel_work_sync() to make sure the work tipc_net_finalize_work() was last queued and it must be completed by calling cancel_work_sync().

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Aug 5, 2026
EPSS
0.2% · 21th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2022-49696

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

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.

VendorProduct
linuxlinux 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.83 and later · before 5.5
  • linux linux kernel5.9.14 and later · before 5.10.127
  • linux linux kernel5.11 and later · before 5.15.51
  • linux linux kernel5.16 and later · before 5.18.8
  • linux linux kernel5.19

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

    • fdc1416c21992ea7b4737123c8aa8c7424a1a540, 1716c9bd567bc6cdb3d18be78f36941a306b708d, 5.10affected
    • d966ddcc38217a6110a6a0ff37ad2dee7d42e23e and later · before 361c5521c1e49843b710f455cae3c0a50b714323affected · git
    • d966ddcc38217a6110a6a0ff37ad2dee7d42e23e and later · before cd7789e659e84f137631dc1f5ec8d794f2700e6caffected · git
    • d966ddcc38217a6110a6a0ff37ad2dee7d42e23e and later · before 8b246ddd394d7d9640816611693b0096b998e27aaffected · git
    • d966ddcc38217a6110a6a0ff37ad2dee7d42e23e and later · before 911600bf5a5e84bfda4d33ee32acc75ecf6159f0affected · git
    • 5.4.83 and later · before 5.5affected · semver
    • 5.9.14 and later · before 5.10affected · semver
    • before 5.10not affected · semver
    • 5.10.127 and later · up to and including 5.10.*not affected · semver
    • 5.15.51 and later · up to and including 5.15.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.18.14-15.18.14-1
Red Hat:rhel_aus:8.4::baseosbpftoolbefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseosbpftool-debuginfobefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernelbefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-abi-stablelistsbefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-corebefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debugbefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-corebefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-debuginfobefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-develbefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-modulesbefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-modules-extrabefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debuginfobefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-develbefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-docbefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-modulesbefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-modules-extrabefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-toolsbefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-tools-debuginfobefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-tools-libsbefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseosperfbefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseosperf-debuginfobefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4
Red Hat:rhel_aus:8.4::baseospython3-perfbefore 0:4.18.0-305.159.1.el8_40:4.18.0-305.159.1.el8_4

+85

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-49694Feb 26, 2025 · block: disable the elevator int del_gendisk
    31Monitor
  • ← EarlierCVE-2022-49695Feb 26, 2025 · igb: fix a use-after-free issue in igb_clean_tx_ring
    31Monitor
  • Later →CVE-2022-49697Feb 26, 2025 · bpf: Fix request_sock leak in sk lookup helpers
    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 / packageFixed versionSource
Linux Linux361c5521c1e49843b710f455cae3c0a50b714323Vendor (CNA)
Linux Linux5.10Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux8b246ddd394d7d9640816611693b0096b998e27aVendor (CNA)
Linux Linux911600bf5a5e84bfda4d33ee32acc75ecf6159f0Vendor (CNA)
Linux Linuxcd7789e659e84f137631dc1f5ec8d794f2700e6cVendor (CNA)
debian:linux5.18.14-1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:5.14.0-70.134.1.rt21.206.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-core0:5.14.0-70.134.1.rt21.206.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:5.14.0-70.134.1.rt21.206.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:5.14.0-70.134.1.rt21.206.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:5.14.0-70.134.1.rt21.206.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:5.14.0-70.134.1.rt21.206.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:5.14.0-70.134.1.rt21.206.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules0:5.14.0-70.134.1.rt21.206.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules-extra0:5.14.0-70.134.1.rt21.206.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debuginfo0:5.14.0-70.134.1.rt21.206.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debuginfo-common-x86_640:5.14.0-70.134.1.rt21.206.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-devel0:5.14.0-70.134.1.rt21.206.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage 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.

EPSS, last 120 days

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.

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

  • 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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

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.

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

Vulnerable

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

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&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

  1. Fix✗ → ✓

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

References

All records