Vulnerability in linux-aws-5.15 (UBUNTU-CVE-2023-52633)
Summary
Vulnerability in linux-aws-5.15 (UBUNTU-CVE-2023-52633). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.15.0-1061.67~20.04.1 or later.
Original description
The description as published by the source.
In the Linux kernel, the following vulnerability has been resolved: um: time-travel: fix time corruption In 'basic' time-travel mode (without =inf-cpu or =ext), we still get timer interrupts. These can happen at arbitrary points in time, i.e. while in timer_read(), which pushes time forward just a little bit. Then, if we happen to get the interrupt after calculating the new time to push to, but before actually finishing that, the interrupt will set the time to a value that's incompatible with the forward, and we'll crash because time goes backwards when we do the forwarding. Fix this by reading the time_travel_time, calculating the adjustment, and doing the adjustment all with interrupts disabled.
Source: OSV.dev (Open Source Vulnerabilities) OSV
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-2023-52633 has been found in linux-aws-5.15.
Risk of unauthorized operations or information disclosure.
What to do: upgrade linux-aws-5.15 to 5.15.0-1061.67~20.04.1 or later.
If unsure, ask your IT team or search "linux-aws-5.15 UBUNTU-CVE-2023-52633" on the vendor's site.
UBUNTU-CVE-2023-52633 (linux-aws-5.15)
Attack vector: local
Patched: 5.15.0-1061.67~20.04.1 — apply immediately
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.
A vulnerability (unclassified) exists in linux-aws-5.15.
Check the vendor advisory for the affected versions of linux-aws-5.15.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.15.0-1061.67~20.04.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'linux-aws-5.15' . 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
-
1Identify exposure identify
grep -r 'linux-aws-5.15' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
linux-aws-5.15を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade linux-aws-5.15 to 5.15.0-1061.67~20.04.1ステージング環境で 5.15.0-1061.67~20.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- report ubuntu.com
- report git.kernel.org
- report git.kernel.org
- report git.kernel.org
- report git.kernel.org
- report git.kernel.org
- report git.kernel.org
- report cve.org