BlackTreeIndependent security intelligence

Full vulnerability report · 2025

CVE-2022-50346High confidence

ext4: init quota for 'old.inode' in 'ext4_rename'

Linux · Linux

5.5MediumCVSS 3.1

Recommended action

Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

9 package states

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu release	Source package	Vendor state	Fixed version	Evidence
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-hwe-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-intel`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency-hwe-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 10 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 10 Sept 2026

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current

ENISA EUVD identifier

EUVD-2022-55616

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state: Present in the current official mapping
Known exploitation: Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score: Not supplied in the stored EUVD record
Advisory evidence: No linked advisory details stored yet

Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ext4: init quota for 'old.inode' in 'ext4_rename' Syzbot found the following issue: ext4_parse_param: s_want_extra_isize=128 ext4_inode_info_init: s_want_extra_isize=32 ext4_rename: old.inode=ffff88823869a2c8 old.dir=ffff888238699828 new.inode=ffff88823869d7e8 new.dir=ffff888238699828 __ext4_mark_inode_dirty: inode=ffff888238699828 ea_isize=32 want_ea_size=128 __ext4_mark_inode_dirty: inode=ffff88823869a2c8 ea_isize=32 want_ea_size=128 ext4_xattr_block_set: inode=ffff88823869a2c8 ------------[ cut here ]------------ WARNING: CPU: 13 PID: 2234 at fs/ext4/xattr.c:2070 ext4_xattr_block_set.cold+0x22/0x980 Modules linked in: RIP: 0010:ext4_xattr_block_set.cold+0x22/0x980 RSP: 0018:ffff888227d3f3b0 EFLAGS: 00010202 RAX: 0000000000000001 RBX: ffff88823007a000 RCX: 0000000000000000 RDX: 0000000000000a03 RSI: 0000000000000040 RDI: ffff888230078178 RBP: 0000000000000000 R08: 000000000000002c R09: ffffed1075c7df8e R10: ffff8883ae3efc6b R11: ffffed1075c7df8d R12: 0000000000000000 R13: ffff88823869a2c8 R14: ffff8881012e0460 R15: dffffc0000000000 FS: 00007f350ac1f740(0000) GS:ffff8883ae200000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f350a6ed6a0 CR3: 0000000237456000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? ext4_xattr_set_entry+0x3b7/0x2320 ? ext4_xattr_block_set+0x0/0x2020 ? ext4_xattr_set_entry+0x0/0x2320 ? ext4_xattr_check_entries+0x77/0x310 ? ext4_xattr_ibody_set+0x23b/0x340 ext4_xattr_move_to_block+0x594/0x720 ext4_expand_extra_isize_ea+0x59a/0x10f0 __ext4_expand_extra_isize+0x278/0x3f0 __ext4_mark_inode_dirty.cold+0x347/0x410 ext4_rename+0xed3/0x174f vfs_rename+0x13a7/0x2510 do_renameat2+0x55d/0x920 __x64_sys_rename+0x7d/0xb0 do_syscall_64+0x3b/0xa0 entry_SYSCALL_64_after_hwframe+0x72/0xdc As 'ext4_rename' will modify 'old.inode' ctime and mark inode dirty, which may trigger expand 'extra_isize' and allocate block. If inode didn't init quota will lead to warning. To solve above issue, init 'old.inode' firstly in 'ext4_rename'.

What

Why

The product uses or accesses a resource that has not been initialized.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The product uses or accesses a resource that has not been initialized.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → Use of Uninitialized Resource → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-908 ↗
CWE-908: Use of Uninitialized Resource. The product uses or accesses a resource that has not been initialized.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

CWE-908

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2022-55616Official EUVD mapping

0 linked advisory records.

Official EUVD record

BSI · German · WID-SEC-W-2026-0349Dell Avamar und NetWorker: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Avamar und Dell NetWorker ausnutzen, um Angriffe zu starten, die die Integrität, Vertraulichkeit und Verfügbarkeit von Systemen beeinträchtigen.

Official advisory

BSI · German · WID-SEC-W-2025-2077Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0921Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-50324 Référence CVE CVE-2022-50328 https://www.cve.org/CVERecord?id=CVE-2022-50328 Référence CVE CVE-2022-50329 https://www.cve.org/CVERecord?id=CVE-2022-50329 Référence CVE CVE-2022-50330 https://www.cve.org/CVERecord?id=CVE-2022-50330 Référence CVE CVE-2022-50331 https://www.cve.org/CVERecord?id=CVE-2022-50331 Référence CVE CVE-2022-50333 https://www.cve.org/CVERecord?id=CVE-2022-50333 Référence CVE CVE-2022-50340 https://www.cve.org/CVERecord?id=CVE-2022-50340 Référence CVE CVE-2022-50342 https://www.cve.org/CVERecord?id=CVE-2022-50342 Référence CVE CVE-2022-50344 https://www.cve.org/CVERecord?id=CVE-2022-50344 Référence CVE CVE-2022-50346 https://www.cve.org/CVERecord?id=CVE-2022-50346 Référence CVE CVE-2022-50347 https://www.cve.org/CVERecord?id=CVE-2022-50347 Référence CVE CVE-2022-50348 https://www.cve.org/CVERecord?id=CVE-2022-50348 Référence CVE CVE-2022-50349 https://www.cve.org/CVERecord?id=CVE-2022-50349 Référence CVE CVE-2022-50351 https://www.cve.org/CVERecord?id=CVE-2022-50351 Référence CVE CVE-2022-50353 https://www.cve.org/CVERecord?id=CVE-2022-50353 Référence CVE CVE-2022-50355 https://www.cve.org/CVERecord?id=CVE-2022-50355 Référence CVE CVE-2022-50358 https://www.cve.org/CVERecord?id=CVE-2022-50358 Référence CVE CVE-2022-50359 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0895Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-50328 Référence CVE CVE-2022-50329 https://www.cve.org/CVERecord?id=CVE-2022-50329 Référence CVE CVE-2022-50330 https://www.cve.org/CVERecord?id=CVE-2022-50330 Référence CVE CVE-2022-50331 https://www.cve.org/CVERecord?id=CVE-2022-50331 Référence CVE CVE-2022-50333 https://www.cve.org/CVERecord?id=CVE-2022-50333 Référence CVE CVE-2022-50339 https://www.cve.org/CVERecord?id=CVE-2022-50339 Référence CVE CVE-2022-50340 https://www.cve.org/CVERecord?id=CVE-2022-50340 Référence CVE CVE-2022-50342 https://www.cve.org/CVERecord?id=CVE-2022-50342 Référence CVE CVE-2022-50344 https://www.cve.org/CVERecord?id=CVE-2022-50344 Référence CVE CVE-2022-50346 https://www.cve.org/CVERecord?id=CVE-2022-50346 Référence CVE CVE-2022-50347 https://www.cve.org/CVERecord?id=CVE-2022-50347 Référence CVE CVE-2022-50348 https://www.cve.org/CVERecord?id=CVE-2022-50348 Référence CVE CVE-2022-50349 https://www.cve.org/CVERecord?id=CVE-2022-50349 Référence CVE CVE-2022-50351 https://www.cve.org/CVERecord?id=CVE-2022-50351 Référence CVE CVE-2022-50352 https://www.cve.org/CVERecord?id=CVE-2022-50352 Référence CVE CVE-2022-50353 https://www.cve.org/CVERecord?id=CVE-2022-50353 Référence CVE CVE-2022-50354 https://www.cve.org/CVERecord?id=CVE-2022-50354 Référence CVE CVE-2022-50355 https://www.cve.org/CVERecord?id=

Official advisory

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e < 67f6d5a4043f3db0c6bb0e14a0d97a7be8bfb8b5; 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e < 33fd7031d634f3b46e59f61adfbb0ea9fe514fef; 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e < 7dfb8259f66faafa68d23a261b284d2c2c67649b; 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e < f263e349bacc2f303526dcfa61c4bc50132418b1; 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e < 84a2f2ed49d6a4d92b354219077434c57d334620; 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e < def7a39091e60e1c4a2f623629082a00092602be; 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e < 135ba9146f4d38abed48a540ef8a8770ff0bd34f; 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e < 13271fbbe85d73a7c47058f56a52f2a7f00d6e39
Fixed: < 2.6.23; 4.9.337 ≤ 4.9.*; 4.14.303 ≤ 4.14.*; 4.19.270 ≤ 4.19.*; 5.4.229 ≤ 5.4.*; 5.10.163 ≤ 5.10.*; 5.15.87 ≤ 5.15.*; 6.0.18 ≤ 6.0.*
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 16 Sept 2025 · Last source change 11 May 2026, 19:17 UTC · CWE-908 · Use of Uninitialized Resource

CVE recordCVE.org · 5.2

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2022-55616

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceCISA ADP

NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2025-09-16CVE published

2026-05-11Fixed release or patch reference recorded

ENISA EUVD · EUVD-2022-55616↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

ext4: init quota for 'old.inode' in 'ext4_rename'

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2022-55616

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.