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

Vulnerability in linux-hwe-edge

UBUNTU-CVE-2022-49456 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-49456 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-49456" on the vendor's site.

UBUNTU-CVE-2022-49456 (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: bonding: fix missed rcu protection When removing the rcu_read_lock in bond_ethtool_get_ts_info() as discussed [1], I didn't notice it could be called via setsockopt, which doesn't hold rcu lock, as syzbot pointed: stack backtrace: CPU: 0 PID: 3599 Comm: syz-executor317 Not tainted 5.18.0-rc5-syzkaller-01392-g01f4685797a5 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 bond_option_active_slave_get_rcu include/net/bonding.h:353 [inline] bond_ethtool_get_ts_info+0x32c/0x3a0 drivers/net/bonding/bond_main.c:5595 __ethtool_get_ts_info+0x173/0x240 net/ethtool/common.c:554 ethtool_get_phc_vclocks+0x99/0x110 net/ethtool/common.c:568 sock_timestamping_bind_phc net/core/sock.c:869 [inline] sock_set_timestamping+0x3a3/0x7e0 net/core/sock.c:916 sock_setsockopt+0x543/0x2ec0 net/core/sock.c:1221 __sys_setsockopt+0x55e/0x6a0 net/socket.c:2223 __do_sys_setsockopt net/socket.c:2238 [inline] __se_sys_setsockopt net/socket.c:2235 [inline] _x64_sys_setsockopt+0xba/0x150 net/socket.c:2235 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f8902c8eb39 Fix it by adding rcu_read_lock and take a ref on the real_dev. Since dev…

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