# GSD-2022-1006310: ext4: add EXT4_INODE_HAS_XATTR_SPACE macro in xattr.h


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Sep 2022

## What is GSD-2022-1006310?

GSD-2022-1006310 is a vulnerability in Kernel, published on 17 Sep 2022. 

### Official description

ext4: add EXT4_INODE_HAS_XATTR_SPACE macro in xattr.h

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.9.326 by commit 214c68423fd632646c68f3ec8b3c2602cf8273f3. For more details please see the references link.

## Which versions are affected by GSD-2022-1006310?

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-2022-1006310?

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

## Is GSD-2022-1006310 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2022-1006310 and fix it if it is affected.

What it is: GSD-2022-1006310 is a vulnerability in Kernel, published on 17 Sep 2022. 
Exploitation: There is no known exploitation of GSD-2022-1006310 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-2022-1006310/ (Markdown: https://insights.sbomify.com/GSD-2022-1006310/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2022-1006310

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