Skip to content

Fix nil deref in HandleUEContextReleaseComplete#756

Merged
gab-arrobo merged 1 commit into
omec-project:mainfrom
gab-arrobo:fix-nil-deref
Jul 14, 2026
Merged

Fix nil deref in HandleUEContextReleaseComplete#756
gab-arrobo merged 1 commit into
omec-project:mainfrom
gab-arrobo:fix-nil-deref

Conversation

@gab-arrobo

Copy link
Copy Markdown
Contributor

No description provided.

@gab-arrobo
gab-arrobo requested review from a team and Copilot July 14, 2026 21:21
Signed-off-by: Arrobo, Gabriel <gabriel.arrobo@intel.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR addresses a nil dereference risk in HandleUEContextReleaseComplete by ensuring the access type used for ongoing-procedure lookup/reset is taken from the RAN context that triggered the release, rather than being inferred from UE connection state. It also finalizes the project version from a -dev suffix to a release version.

Changes:

  • Use ran.AnType when reading/resetting amfUe “OnGoing” procedure state in HandleUEContextReleaseComplete to avoid invalid access-type selection (and subsequent nil deref).
  • Update the VERSION file from 3.1.3-dev to 3.1.3.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
VERSION Bumps version string to the 3.1.3 release.
ngap/handler.go Fixes access-type selection when checking/resetting ongoing procedure during UE Context Release Complete handling.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@gab-arrobo
gab-arrobo merged commit 9b38ab8 into omec-project:main Jul 14, 2026
12 checks passed
@gab-arrobo
gab-arrobo deleted the fix-nil-deref branch July 14, 2026 21:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants