# GSD-2021-1001468: netrom: Decrease sock refcount when sock timers expire

> A use-after-free vulnerability in the Linux kernel netrom module allows attackers to cause denial of service or potentially execute code.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2021

## What is GSD-2021-1001468?

GSD-2021-1001468 is an use after free vulnerability in Kernel, published on 3 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

netrom: Decrease sock refcount when sock timers expire

This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v4.4.277 by commit 853262355518cd1247515b74e83fabf038aa6c29, it was introduced in version v4.4.173 by commit ce29e8a259de767f7210d346ad2b031cb8ab2732. For more details please see the references link.

## Which versions are affected by GSD-2021-1001468?

1 open source package ship an affected version, including Kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Kernel` | Linux | All versions | None |

## How do I fix GSD-2021-1001468?

No fix has been published for GSD-2021-1001468 yet. Limit exposure of the affected software until one is available.

## Is GSD-2021-1001468 being exploited?

There is no known exploitation of GSD-2021-1001468 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2021-1001468 and fix it if it is affected.

What it is: GSD-2021-1001468 is an use after free vulnerability in Kernel, published on 3 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GSD-2021-1001468 in the wild and no public exploit code.

Affected packages and fixed versions:
- Kernel (Linux): affected all versions; no fix listed

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/GSD-2021-1001468/ (Markdown: https://insights.sbomify.com/GSD-2021-1001468/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2021-1001468

---
From sbomify Insights: https://insights.sbomify.com/GSD-2021-1001468/
Summaries are generated and may contain mistakes; the official description above is the record.