LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50080: tee: add overflow check in register_shm_helper()

In the Linux kernel, the following vulnerability has been resolved: tee: add overflow check in register_shm_helper() With special lengths supplied by user space, register_shm_helper() has an integer overflow when calculating the number of pages covered by a supplied user space memory region. This causes internal_get_user_pages_fast() a helper function of pin_user_pages_fast() to do a NULL pointer dereference: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010 Modules linked in: CPU: 1 PID: 173 Comm: optee_example_a Not tainted 5.19.0 #11 Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 pc : internal_get_user_pages_fast+0x474/0xa80 Call trace: internal_get_user_pages_fast+0x474/0xa80 pin_user_pages_fast+0x24/0x4c register_shm_helper+0x194/0x330 tee_shm_register_user_buf+0x78/0x120 tee_ioctl+0xd0/0x11a0 __arm64_sys_ioctl+0xa8/0xec invoke_syscall+0x48/0x114 Fix this by adding an an explicit call to access_ok() in tee_shm_register_user_buf() to catch an invalid user space address early.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50080 is a Linux kernel flaw in TEE shared-memory registration. A specially sized user-space memory request can trigger an integer overflow and kernel NULL pointer dereference, likely causing a local denial of service on affected systems.

Executive priority

Treat this as a scheduled but important kernel maintenance item, higher priority for systems using trusted execution environments. There is no cited active exploitation, but kernel crashes can affect availability and may carry operational risk on appliances or embedded platforms.

Technical view

The bug is in register_shm_helper() / tee_shm_register_user_buf(). Length arithmetic for a user-space memory region can overflow before pin_user_pages_fast(), reaching internal_get_user_pages_fast() with invalid state. The kernel fix adds an explicit access_ok() check to reject invalid user-space addresses earlier.

Likely exposure

Exposure is most relevant to Linux systems with TEE support reachable from local user space, including OP-TEE-related deployments. The source lists Linux kernel versions beginning at 4.16 and several stable branches as affected, but product-specific distribution status must be confirmed with vendor advisories.

Exploitation context

The provided sources do not show active exploitation, public exploit availability, or KEV listing. The described trigger requires user-space supplied lengths and access to the relevant TEE ioctl path, so this should be treated as a local kernel stability risk unless new evidence emerges.

Researcher notes

Evidence is limited to the CVE record and upstream stable commit references. No CVSS, CWE, exploit status, or distribution package matrix is provided. Avoid assuming privilege escalation; the cited failure mode is a NULL pointer dereference after arithmetic overflow in the TEE shared-memory path.

Mitigation direction

  • Apply Linux kernel or distribution updates containing the referenced stable fixes.
  • Prioritize hosts using TEE, OP-TEE, secure-world integrations, or exposed tee device nodes.
  • Check vendor kernel advisories for exact package versions and backport status.
  • Restrict local access to TEE device nodes according to least privilege.
  • Reboot into the fixed kernel after patching.

Validation and detection

  • Inventory kernel versions and map them to vendor-fixed builds.
  • Confirm whether TEE/OP-TEE drivers and device nodes are present.
  • Review local permissions for TEE character devices.
  • Verify the running kernel includes the access_ok() fix or vendor backport.
  • Monitor for unexplained kernel NULL dereference crashes in TEE paths.
Prepared
Confidence
medium
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50080 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux033ddf12bcf5326b93bd604f50a7474a434a35f9, 033ddf12bcf5326b93bd604f50a7474a434a35f9, 033ddf12bcf5326b93bd604f50a7474a434a35f9, 033ddf12bcf5326b93bd604f50a7474a434a35f9, 033ddf12bcf5326b93bd604f50a7474a434a35f9, 033ddf12bcf5326b93bd604f50a7474a434a35f9, 033ddf12bcf5326b93bd604f50a7474a434a35f9unaffected
LinuxLinux4.16, 0, 4.19.256, 5.4.211, 5.10.137, 5.15.62, 5.18.19, 5.19.3, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.