CVE-2022-49366

Service interruption via leaked POSIX ACL references

Published Feb 26, 2025 · Updated May 11, 2026

Memory leak in the ksmbd ACL permission path in Linux allows local users to exhaust kernel memory through repeated permission checks. The smb_check_perm_dacl function retains a get_acl reference when an ACL identifier equals the requester's user identifier and control jumps directly to check_access_bits without releasing posix_acls. The affected path requires ksmbd ACL permission evaluation, and repeated triggering can interrupt service by consuming kernel memory.

CVSS severity5.5
Medium
EPSS probability0.26%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Memory leak in the ksmbd ACL permission path in Linux allows local users to exhaust kernel memory through repeated permission checks. The smb_check_perm_dacl function retains a get_acl reference when an ACL identifier equals the requester's user identifier and control jumps directly to check_access_bits without releasing posix_acls. The affected path requires ksmbd ACL permission evaluation, and repeated triggering can interrupt service by consuming kernel memory.

The record

CVE
CVE-2022-49366
Published
Feb 26, 2025
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 26, 2025CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.15
  2. Affected versionversion=777cad1604d68ed4379ec899d1f7d2f6a29f01f0 <248d71b440aef829f5cc5f6545ca113ef5062900
  3. Affected versionversion=777cad1604d68ed4379ec899d1f7d2f6a29f01f0 <9758a6653c27867d810de02b4e5697163dda9883
  4. Affected versionversion=777cad1604d68ed4379ec899d1f7d2f6a29f01f0 <cf824b95c12a1abacadbc2d069931963221a3414
  5. Affected versionversion=777cad1604d68ed4379ec899d1f7d2f6a29f01f0 <d21a580dafc69aa04f46e6099616146a536b0724

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.15; version=777cad1604d68ed4379ec899d1f7d2f6a29f01f0 <248d71b440aef829f5cc5f6545ca113ef5062900; version=777cad1604d68ed4379ec899d1f7d2f6a29f01f0 <9758a6653c27867d810de02b4e5697163dda9883; version=777cad1604d68ed4379ec899d1f7d2f6a29f01f0 <cf824b95c12a1abacadbc2d069931963221a3414; version=777cad1604d68ed4379ec899d1f7d2f6a29f01f0 <d21a580dafc69aa04f46e6099616146a536b0724

Published CVSS scores

5.5CISA-ADPCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo