# SUSE-SU-2015:1612-1: Security update for kernel-source

> A kernel update fixes a Btrfs space initialization bug that could cause denial of service via ENOSPC errors.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Sep 2015

## What is SUSE-SU-2015:1612-1?

SUSE-SU-2015:1612-1 is a vulnerability in kernel-default, published on 10 Sep 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The SUSE Linux Enterprise 12 kernel was updated to version 3.12.44-52.13
to receive various bugfixes.

- Btrfs: don't initialize a space info as full to prevent ENOSPC (bsc#944001).
- kernel/kvm: Fix MSA3/MSA4 detection (bsc#936916, LTC#127868).
- zcrypt: Fixed reset and interrupt handling of AP queues (bsc#936916,
  LTC#126491).
- Update s390x kABI files after gcc update (bsc#924525).

## Which versions are affected by SUSE-SU-2015:1612-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel-default` | SUSE:Linux Enterprise Desktop 12 | All versions | 3.12.44-52.18.1 |
| `kernel-source` | SUSE:Linux Enterprise Desktop 12 | All versions | 3.12.44-52.18.1 |
| `kernel-syms` | SUSE:Linux Enterprise Desktop 12 | All versions | 3.12.44-52.18.1 |
| `kernel-xen` | SUSE:Linux Enterprise Desktop 12 | All versions | 3.12.44-52.18.1 |
| `kgraft-patch-SLE12_Update_7` | SUSE:Linux Enterprise Live Patching 12 | All versions | 1-4.2 |
| `kernel-ec2` | SUSE:Linux Enterprise Module for Public Cloud 12 | All versions | 3.12.44-52.18.1 |
| `kernel-default` | SUSE:Linux Enterprise Server 12 | All versions | 3.12.44-52.18.1 |
| `kernel-source` | SUSE:Linux Enterprise Server 12 | All versions | 3.12.44-52.18.1 |
| `kernel-syms` | SUSE:Linux Enterprise Server 12 | All versions | 3.12.44-52.18.1 |
| `kernel-xen` | SUSE:Linux Enterprise Server 12 | All versions | 3.12.44-52.18.1 |
| `kernel-default` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 3.12.44-52.18.1 |
| `kernel-source` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 3.12.44-52.18.1 |
| `kernel-syms` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 3.12.44-52.18.1 |
| `kernel-xen` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 3.12.44-52.18.1 |
| `kernel-docs` | SUSE:Linux Enterprise Software Development Kit 12 | All versions | 3.12.44-52.18.3 |
| `kernel-obs-build` | SUSE:Linux Enterprise Software Development Kit 12 | All versions | 3.12.44-52.18.1 |
| `kernel-default` | SUSE:Linux Enterprise Workstation Extension 12 | All versions | 3.12.44-52.18.1 |

## How do I fix SUSE-SU-2015:1612-1?

Apply the vendor's patch.

## Is SUSE-SU-2015:1612-1 being exploited?

There is no known exploitation of SUSE-SU-2015:1612-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2015:1612-1 and fix it if it is affected.

What it is: SUSE-SU-2015:1612-1 is a vulnerability in kernel-default, published on 10 Sep 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2015:1612-1 in the wild and no public exploit code.

Affected product: kernel-default. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/SUSE-SU-2015-1612-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2015-1612-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2015:1612-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2015-1612-1/
Summaries are generated and may contain mistakes; the official description above is the record.