Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52989: firewire: fix memory leak for payload of request subaction to IEC 61883-1 FCP region

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.26% (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 356ff89acdbe6a66019154bc7eb2d300f5b15103, 531390a243ef47448f8bad01c186c2787666bf4d, 53785fd9b315583cf029e39f72b73d23704a2253.

Low priority for now. Upgrade to Linux Linux 356ff89acdbe6a66019154bc7eb2d300f5b15103, 531390a243ef47448f8bad01c186c2787666bf4d, 53785fd9b315583cf029e39f72b73d23704a2253 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: firewire: fix memory leak for payload of request subaction to IEC 61883-1 FCP region This patch is fix for Linux kernel v2.6.33 or later. For request subaction to IEC 61883-1 FCP region, Linux FireWire subsystem have had an issue of use-after-free. The subsystem allows multiple user space listeners to the region, while data of the payload was likely released before the listeners execute read(2) to access to it for copying to user space. The issue was fixed by a commit 281e20323ab7 ("firewire: core: fix use-after-free regression in FCP handler"). The object of payload is duplicated in kernel space for each listener. When the listener executes ioctl(2) with FW_CDEV_IOC_SEND_RESPONSE request, the object is going to be released. However, it causes memory leak since the commit relies on call of release_request() in drivers/firewire/core-cdev.c. Against the expectation, the function is never called due to the design of release_client_resource(). The function delegates release task to caller when called with non-NULL fourth argument. The implementation of ioctl_send_response() is the case. It should release the object explicitly. This commit fixes the bug.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Mar 27, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 18th percentile

Report tools

JSON

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.

Follow CVE-2023-52989

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

  • 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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
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 kernel2.6.33 and later · before 4.14.306
  • linux linux kernel4.15 and later · before 4.19.273
  • linux linux kernel4.20 and later · before 5.4.232
  • linux linux kernel5.5 and later · before 5.10.168
  • linux linux kernel5.11 and later · before 5.15.93
  • linux linux kernel5.16 and later · before 6.1.11
  • linux linux kernel6.2

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

    • 2.6.33affected
    • 281e20323ab72180137824a298ee9e21e6f9acf6 and later · before b2cd3947d116bb9ba7ff097b5fc747a8956764dbaffected · git
    • 281e20323ab72180137824a298ee9e21e6f9acf6 and later · before 356ff89acdbe6a66019154bc7eb2d300f5b15103affected · git
    • 281e20323ab72180137824a298ee9e21e6f9acf6 and later · before 53785fd9b315583cf029e39f72b73d23704a2253affected · git
    • 281e20323ab72180137824a298ee9e21e6f9acf6 and later · before d5a2dcee53fa6e6e2822f93cb3f1b0cd23163beeaffected · git
    • 281e20323ab72180137824a298ee9e21e6f9acf6 and later · before 5f4543c9382ae2d5062f6aa4fecae0c9258d0b0eaffected · git
    • 281e20323ab72180137824a298ee9e21e6f9acf6 and later · before c8bdc88216f09cb7387fedbdf613524367328616affected · git
    • 281e20323ab72180137824a298ee9e21e6f9acf6 and later · before 531390a243ef47448f8bad01c186c2787666bf4daffected · git
    • before 2.6.33not affected · semver
    • 4.14.306 and later · up to and including 4.14.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.11-16.1.11-1

Same product

linux: all records

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-2023-52985Mar 27, 2025 · arm64: dts: imx8mm-verdin: Do not power down eth-phy
    22Monitor
  • ← EarlierCVE-2023-52988Mar 27, 2025 · ALSA: hda/via: Avoid potential array out-of-bound in add_secret_dac_path()
    31Monitor
  • Later →CVE-2023-52991Mar 27, 2025 · net: fix NULL pointer in skb_segment_list
    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 Linux356ff89acdbe6a66019154bc7eb2d300f5b15103Vendor (CNA)
Linux Linux531390a243ef47448f8bad01c186c2787666bf4dVendor (CNA)
Linux Linux53785fd9b315583cf029e39f72b73d23704a2253Vendor (CNA)
Linux Linux5f4543c9382ae2d5062f6aa4fecae0c9258d0b0eVendor (CNA)
Linux Linuxb2cd3947d116bb9ba7ff097b5fc747a8956764dbVendor (CNA)
Linux Linuxc8bdc88216f09cb7387fedbdf613524367328616Vendor (CNA)
Linux Linuxd5a2dcee53fa6e6e2822f93cb3f1b0cd23163beeVendor (CNA)
debian:linux6.1.11-1 · Debian:12Package 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.

No commit or PR link among the references.

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

  • 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 Lifetime

CVSS 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

  1. Fix✗ → ✓

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

References

Show all references (6 more)

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

All records