Skip to content
This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2022-49511 →
Unrated

Vulnerability in linux-hwe-edge

UBUNTU-CVE-2022-49511 First seen on SecPulse

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2022-49511 has been found in linux-hwe-edge.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "linux-hwe-edge UBUNTU-CVE-2022-49511" on the vendor's site.

UBUNTU-CVE-2022-49511 (linux-hwe-edge)
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

What is the problem

A vulnerability (unclassified) exists in linux-hwe-edge.

Affected scope

Check the vendor advisory for the affected versions of linux-hwe-edge.

Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

How to fix

Update to the patched release per vendor advisory.

Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'linux-hwe-edge' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposureidentify
    grep -r 'linux-hwe-edge' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で linux-hwe-edge を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verificationverify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

EcosystemPackageAffectedFixed
Ubuntu:16.04:LTS linux-hwe-edge
All versions
—
Ubuntu:18.04:LTS linux-aws-5.0
All versions
—
Ubuntu:18.04:LTS linux-aws-5.3
All versions
—
Ubuntu:18.04:LTS linux-azure
All versions
—
Ubuntu:18.04:LTS linux-azure-5.3
All versions
—
Ubuntu:18.04:LTS linux-azure-edge
All versions
—
Ubuntu:18.04:LTS linux-gcp
All versions
—
Ubuntu:18.04:LTS linux-gcp-5.3
All versions
—
Ubuntu:18.04:LTS linux-gke-4.15
All versions
—
Ubuntu:18.04:LTS linux-gke-5.4
All versions
—
Ubuntu:18.04:LTS linux-gkeop-5.4
All versions
—
Ubuntu:18.04:LTS linux-hwe
All versions
—
Ubuntu:18.04:LTS linux-hwe-edge
All versions
—
Ubuntu:18.04:LTS linux-oem
All versions
—
Ubuntu:18.04:LTS linux-oracle-5.0
All versions
—
Ubuntu:18.04:LTS linux-oracle-5.3
All versions
—
Ubuntu:20.04:LTS linux-aws-5.11
All versions
—
Ubuntu:20.04:LTS linux-aws-5.13
All versions
—
Ubuntu:20.04:LTS linux-aws-5.8
All versions
—
Ubuntu:20.04:LTS linux-azure-5.11
All versions
—
Ubuntu:20.04:LTS linux-azure-5.13
All versions
—
Ubuntu:20.04:LTS linux-azure-5.8
All versions
—
Ubuntu:20.04:LTS linux-azure-fde
All versions
—
Ubuntu:20.04:LTS linux-gcp-5.11
All versions
—
Ubuntu:20.04:LTS linux-gcp-5.13
All versions
—
Ubuntu:20.04:LTS linux-gcp-5.8
All versions
—
Ubuntu:20.04:LTS linux-gke
All versions
—
Ubuntu:20.04:LTS linux-gke-5.15
All versions
—
Ubuntu:20.04:LTS linux-gkeop
All versions
—
Ubuntu:20.04:LTS linux-gkeop-5.15
All versions
—
Ubuntu:20.04:LTS linux-hwe-5.11
All versions
—
Ubuntu:20.04:LTS linux-hwe-5.13
All versions
—
Ubuntu:20.04:LTS linux-hwe-5.8
All versions
—
Ubuntu:20.04:LTS linux-intel-5.13
All versions
—
Ubuntu:20.04:LTS linux-oem-5.10
All versions
—
Ubuntu:20.04:LTS linux-oem-5.13
All versions
—
Ubuntu:20.04:LTS linux-oem-5.14
All versions
—
Ubuntu:20.04:LTS linux-oem-5.6
All versions
—
Ubuntu:20.04:LTS linux-oracle-5.11
All versions
—
Ubuntu:20.04:LTS linux-oracle-5.13
All versions
—
Ubuntu:20.04:LTS linux-oracle-5.8
All versions
—
Ubuntu:20.04:LTS linux-raspi2
All versions
—
Ubuntu:20.04:LTS linux-riscv
All versions
—
Ubuntu:20.04:LTS linux-riscv-5.11
All versions
—
Ubuntu:20.04:LTS linux-riscv-5.8
All versions
—
Ubuntu:22.04:LTS linux-allwinner-5.19
All versions
—
Ubuntu:22.04:LTS linux-aws-5.19
All versions
—
Ubuntu:22.04:LTS linux-aws-6.2
All versions
—
Ubuntu:22.04:LTS linux-aws-6.5
All versions
—
Ubuntu:22.04:LTS linux-azure-5.19
All versions
—
Ubuntu:22.04:LTS linux-azure-6.2
All versions
—
Ubuntu:22.04:LTS linux-azure-6.5
All versions
—
Ubuntu:22.04:LTS linux-azure-fde-5.19
All versions
—
Ubuntu:22.04:LTS linux-azure-fde-6.2
All versions
—
Ubuntu:22.04:LTS linux-gcp-5.19
All versions
—
Ubuntu:22.04:LTS linux-gcp-6.2
All versions
—
Ubuntu:22.04:LTS linux-gcp-6.5
All versions
—
Ubuntu:22.04:LTS linux-hwe-5.19
All versions
—
Ubuntu:22.04:LTS linux-hwe-6.2
All versions
—
Ubuntu:22.04:LTS linux-hwe-6.5
All versions
—
Ubuntu:22.04:LTS linux-intel-iot-realtime
All versions
—
Ubuntu:22.04:LTS linux-lowlatency-hwe-5.19
All versions
—
Ubuntu:22.04:LTS linux-lowlatency-hwe-6.2
All versions
—
Ubuntu:22.04:LTS linux-lowlatency-hwe-6.5
All versions
—
Ubuntu:22.04:LTS linux-nvidia-6.2
All versions
—
Ubuntu:22.04:LTS linux-nvidia-6.5
All versions
—
Ubuntu:22.04:LTS linux-oem-5.17
All versions
—
Ubuntu:22.04:LTS linux-oem-6.0
All versions
—
Ubuntu:22.04:LTS linux-oem-6.1
All versions
—
Ubuntu:22.04:LTS linux-oem-6.5
All versions
—
Ubuntu:22.04:LTS linux-oracle-6.5
All versions
—
Ubuntu:22.04:LTS linux-realtime
All versions
—
Ubuntu:22.04:LTS linux-riscv
All versions
—
Ubuntu:22.04:LTS linux-riscv-5.19
All versions
—
Ubuntu:22.04:LTS linux-riscv-6.5
All versions
—
Ubuntu:22.04:LTS linux-starfive-5.19
All versions
—
Ubuntu:22.04:LTS linux-starfive-6.2
All versions
—
Ubuntu:22.04:LTS linux-starfive-6.5
All versions
—
Ubuntu:24.04:LTS linux-raspi-realtime
All versions
—
Original description The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved: fbdev: defio: fix the pagelist corruption Easily hit the below list corruption: == list_add corruption. prev->next should be next (ffffffffc0ceb090), but was ffffec604507edc8. (prev=ffffec604507edc8). WARNING: CPU: 65 PID: 3959 at lib/list_debug.c:26 __list_add_valid+0x53/0x80 CPU: 65 PID: 3959 Comm: fbdev Tainted: G U RIP: 0010:__list_add_valid+0x53/0x80 Call Trace: fb_deferred_io_mkwrite+0xea/0x150 do_page_mkwrite+0x57/0xc0 do_wp_page+0x278/0x2f0 __handle_mm_fault+0xdc2/0x1590 handle_mm_fault+0xdd/0x2c0 do_user_addr_fault+0x1d3/0x650 exc_page_fault+0x77/0x180 ? asm_exc_page_fault+0x8/0x30 asm_exc_page_fault+0x1e/0x30 RIP: 0033:0x7fd98fc8fad1 == Figure out the race happens when one process is adding &page->lru into the pagelist tail in fb_deferred_io_mkwrite(), another process is re-initializing the same &page->lru in fb_deferred_io_fault(), which is not protected by the lock. This fix is to init all the page lists one time during initialization, it not only fixes the list corruption, but also avoids INIT_LIST_HEAD() redundantly. V2: change "int i" to "unsigned int i" (Geert Uytterhoeven)

Source: OSV.dev (Open Source Vulnerabilities) OSV

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details