CVE-2022-49399: tty: goldfish: Use tty_port_destroy() to destroy port
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 241fcb79dd1df276d80b19f5f6acc9eaaaa63309, 326192b99c903a2193d820c30ed936cc2402382c, 45f6ce70abfb7ccf9d787781cbc4c03294a775a1.
Low priority for now. Upgrade to Linux Linux 241fcb79dd1df276d80b19f5f6acc9eaaaa63309, 326192b99c903a2193d820c30ed936cc2402382c, 45f6ce70abfb7ccf9d787781cbc4c03294a775a1 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: tty: goldfish: Use tty_port_destroy() to destroy port In goldfish_tty_probe(), the port initialized through tty_port_init() should be destroyed in error paths.In goldfish_tty_remove(), qtty->port also should be destroyed or else might leak resources. Fix the above by calling tty_port_destroy().
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- —
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%
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.
Is your version affected? Check itNoroxi 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 kernel3.9 and later · before 4.14.283
- linux linux kernel4.15 and later · before 4.19.247
- linux linux kernel4.20 and later · before 5.4.198
- linux linux kernel5.5 and later · before 5.10.122
- linux linux kernel5.11 and later · before 5.15.47
- linux linux kernel5.16 and later · before 5.17.15
- linux linux kernel5.18 and later · before 5.18.4
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
- 3.9affected
- 666b7793d4bfa9f150b5c2007ab48c755ddc53ca and later · before 241fcb79dd1df276d80b19f5f6acc9eaaaa63309affected · git
- 666b7793d4bfa9f150b5c2007ab48c755ddc53ca and later · before 326192b99c903a2193d820c30ed936cc2402382caffected · git
- 666b7793d4bfa9f150b5c2007ab48c755ddc53ca and later · before 9ae3d073f7db5578ae1907544f0c15947e9678e6affected · git
- 666b7793d4bfa9f150b5c2007ab48c755ddc53ca and later · before ee6c33b29e624f515202a31bf6ef0437f26a1867affected · git
- 666b7793d4bfa9f150b5c2007ab48c755ddc53ca and later · before da64f419d7f78272bfe40dde1262602d4ff6b32caffected · git
- 666b7793d4bfa9f150b5c2007ab48c755ddc53ca and later · before 45f6ce70abfb7ccf9d787781cbc4c03294a775a1affected · git
- 666b7793d4bfa9f150b5c2007ab48c755ddc53ca and later · before 4639d1b992de8f37d66f698056875c274efcd45faffected · git
- 666b7793d4bfa9f150b5c2007ab48c755ddc53ca and later · before 507b05063d1b7a1fcb9f7d7c47586fc4f3508f98affected · git
- before 3.9not 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.18.5-1 | 5.18.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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
Published before and after this one in the same product
- ← EarlierCVE-2022-49397Feb 26, 2025 · phy: qcom-qmp: fix struct clk leak on probe errors22Monitor
- ← EarlierCVE-2022-49398Feb 26, 2025 · usb: dwc3: gadget: Replace list_for_each_entry_safe() if using giveback22Monitor
- Later →CVE-2022-49400Feb 26, 2025 · md: Don't set mddev private to NULL in raid0 pers->free22Monitor
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 | 241fcb79dd1df276d80b19f5f6acc9eaaaa63309 | Vendor (CNA) |
| Linux Linux | 326192b99c903a2193d820c30ed936cc2402382c | Vendor (CNA) |
| Linux Linux | 45f6ce70abfb7ccf9d787781cbc4c03294a775a1 | Vendor (CNA) |
| Linux Linux | 4639d1b992de8f37d66f698056875c274efcd45f | Vendor (CNA) |
| Linux Linux | 507b05063d1b7a1fcb9f7d7c47586fc4f3508f98 | Vendor (CNA) |
| Linux Linux | 9ae3d073f7db5578ae1907544f0c15947e9678e6 | Vendor (CNA) |
| Linux Linux | da64f419d7f78272bfe40dde1262602d4ff6b32c | Vendor (CNA) |
| Linux Linux | ee6c33b29e624f515202a31bf6ef0437f26a1867 | Vendor (CNA) |
| debian:linux | 5.18.5-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.
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 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)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/326192b99c903a2193d820c30ed936cc2402382c
- git.kernel.org/stable/c/45f6ce70abfb7ccf9d787781cbc4c03294a775a1
- git.kernel.org/stable/c/4639d1b992de8f37d66f698056875c274efcd45f
- git.kernel.org/stable/c/507b05063d1b7a1fcb9f7d7c47586fc4f3508f98
- git.kernel.org/stable/c/9ae3d073f7db5578ae1907544f0c15947e9678e6
- git.kernel.org/stable/c/da64f419d7f78272bfe40dde1262602d4ff6b32c
- git.kernel.org/stable/c/ee6c33b29e624f515202a31bf6ef0437f26a1867
Vendor advisories and official records. Exploit/PoC links are deliberately left out.