This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2015-7837 →

UBUNTU-CVE-2015-7837

Vulnerability in linux-lts-vivid (UBUNTU-CVE-2015-7837)

Summary

Vulnerability in linux-lts-vivid (UBUNTU-CVE-2015-7837). Data can be tampered with by attackers. Mitigation: upgrade to 3.19.0-74.82~14.04.1 or later.

Original description

The description as published by the source.

The Linux kernel, as used in Red Hat Enterprise Linux 7, kernel-rt, and Enterprise MRG 2 and when booted with UEFI Secure Boot enabled, allows local users to bypass intended securelevel/secureboot restrictions by leveraging improper handling of secure_boot flag across kexec reboot.

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-2015-7837 has been found in linux-lts-vivid.
Data can be tampered with by attackers.
What to do: upgrade linux-lts-vivid to 3.19.0-74.82~14.04.1 or later.
If unsure, ask your IT team or search "linux-lts-vivid UBUNTU-CVE-2015-7837" on the vendor's site.

UBUNTU-CVE-2015-7837 (linux-lts-vivid)
Attack vector: local / no user interaction
Patched: 3.19.0-74.82~14.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.

❓ What is the problem

A vulnerability (unclassified) exists in linux-lts-vivid.

📍 Affected scope

Check the vendor advisory for the affected versions of linux-lts-vivid.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 3.19.0-74.82~14.04.1.

🛡️ 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-lts-vivid' . 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
Identify exposure identify
```
grep -r 'linux-lts-vivid' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で linux-lts-vivid を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade linux-lts-vivid to 3.19.0-74.82~14.04.1
```
ステージング環境で 3.19.0-74.82~14.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:14.04:LTS linux-lts-vivid

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.19.0-74.82~14.04.1"}]}]

Ubuntu:14.04:LTS linux-lts-xenial

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-93.116~14.04.1"}]}]

Ubuntu:16.04:LTS linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-93.116"}]}]

Ubuntu:16.04:LTS linux-aws

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1032.41"}]}]

Ubuntu:16.04:LTS linux-gke

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1028.28"}]}]

Ubuntu:Pro:18.04:LTS linux-aws-5.4